From: "Alexey Zaytsev" <alexey.zaytsev@gmail.com>
To: David Given <dg@cowlark.com>
Cc: linux-sparse@vger.kernel.org, Josh Triplett <josh@kernel.org>
Subject: Re: [PATCH 2/15 v2] Unhardcode byte size being 8 bits.
Date: Thu, 18 Dec 2008 04:24:00 +0300 [thread overview]
Message-ID: <f19298770812171724k6411542fq5baf361d481f927c@mail.gmail.com> (raw)
In-Reply-To: <4949A03A.5060309@cowlark.com>
On Thu, Dec 18, 2008 at 03:58, David Given <dg@cowlark.com> wrote:
> Alexey Zaytsev wrote:
> [...]
>> Please, sign off this patch and the one adding type information to
>> struct instruction.
>
> I'm sorry, I didn't realise you were talking to me!
>
> What do you want me to do? I don't know anything about the sort of
> process you use.
>
Short: You add 'Signed-off-by: David Given <dg@cowlark.com>' to the
end of the patch description. Or if you forgot to do so, you can reply
to the email with this line and the maintainer will add it to the
patch description for you. This bascally means that you are OK with
your work being merget my other people, and also helps to track who
made which changes/bugs, statistics, etc, and some even see it as
having some legal power.
Long: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=Documentation/SubmittingPatches;h=f309d3c6221c3699a0c0b97fbe689faed09e4d2f;hb=HEAD#l282
Sparse seems to use the same procedure as the kernel.
next prev parent reply other threads:[~2008-12-18 1:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-17 20:05 [PATCH 2/15 v2] Unhardcode byte size being 8 bits Alexey Zaytsev
2008-12-17 23:33 ` David Given
2008-12-18 0:33 ` Alexey Zaytsev
2008-12-18 0:58 ` David Given
2008-12-18 1:24 ` Alexey Zaytsev [this message]
2008-12-18 1:10 ` Derek M Jones
2008-12-18 1:52 ` Derek M Jones
2008-12-18 3:11 ` Alexey Zaytsev
2008-12-18 13:05 ` Derek M Jones
2008-12-18 17:07 ` Alexey Zaytsev
2008-12-18 17:12 ` David Given
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=f19298770812171724k6411542fq5baf361d481f927c@mail.gmail.com \
--to=alexey.zaytsev@gmail.com \
--cc=dg@cowlark.com \
--cc=josh@kernel.org \
--cc=linux-sparse@vger.kernel.org \
/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).