linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josh Triplett <josh@freedesktop.org>
To: "Loïc Minier" <lool+kernel@via.ecp.fr>
Cc: linux-sparse@vger.kernel.org
Subject: Re: Debian package; trivial fixes
Date: Tue, 21 Nov 2006 08:51:15 -0800	[thread overview]
Message-ID: <45632E83.80509@freedesktop.org> (raw)
In-Reply-To: <20061109151912.GC8508@bee.dooz.org>

[-- Attachment #1: Type: text/plain, Size: 1017 bytes --]

Loïc Minier wrote:
>  I've prepared and uploaded a Debian package for sparse 0.1:
>     <http://people.dooz.org/~lool/debian/sparse/0.1-1/sid-pbuilder/>

Thanks!

>  Please find attached a trivial fix for .gitignore where "check" wasn't
>  renamed to "sparse".
>
>  It would also be more convenient to create BINDIR automatically on make
>  install.

Thanks for these two fixes.

Sparse follows the same Signed-off-by convention as Linux, so coud you
please supply a Signed-off-by for your patches?  See <http://kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;hb=HEAD;f=Documentation/SubmittingPatches>
for details on the Signed-off-by process and the Developer's Certificate of
Origin.

You might find git convenient for submitting patches.  If you have changes to
Sparse in a git repository, you can create patch mails with "git
format-patch".  git also makes Signed-off-by as simple as adding -s to the
"git commit" or "cg commit" command line.

Thanks,
Josh Triplett


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

  reply	other threads:[~2006-11-21 16:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-09 15:19 Debian package; trivial fixes Loïc Minier
2006-11-21 16:51 ` Josh Triplett [this message]
2006-11-21 17:08 ` Josh Triplett

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=45632E83.80509@freedesktop.org \
    --to=josh@freedesktop.org \
    --cc=linux-sparse@vger.kernel.org \
    --cc=lool+kernel@via.ecp.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).