[PATCH V2 3/6] mtd: bcm47xxnflash: fix message

[Artem Bityutskiy]

On Mon, 2013-02-04 at 09:42 +0100, Rafał Miłecki wrote:
> 2013/2/4 Artem Bityutskiy <dedekind1 at gmail.com>:
> > On Mon, 2013-01-28 at 11:25 +0100, Rafał Miłecki wrote:
> >> From: Hauke Mehrtens <hauke at hauke-m.de>
> >>
> >> This is not a serial flash driver, but a nand flash driver
> >>
> >> Signed-off-by: Hauke Mehrtens <hauke at hauke-m.de>
> >> ---
> >> V2: break line to match 80 chars
> >
> > When sending v2 for individual patches, please, remember 2 things:
> >
> > 1. Keep them part of the original thread (ensure correct In-Reply-To:).
> 
> Whoops, I've to learn how to make that with git send-email.

 --in-reply-to=<identifier>

Pick the identifier from the Message-ID tag of the e-mail you are
replying to. E.g., save the e-mail as hauke.mbox file and do:

$ grep -i '^Message-ID:' hauke.mbox
Message-Id: <1359045599-1305-2-git-send-email-hauke at hauke-m.de>

which means that for this one the 'git send-email' option will be:

--in-reply-to="<1359045599-1305-2-git-send-email-hauke at hauke-m.de>"

> > 2. Add your own signed-off-by.
> 
> It was so trivial... I wasn't sure if it's worth signing-it-by... ;)

Signed-off-by is not about how big were your changes, it roughly
speaking means that you confirm that the source of this patch for you is
Hauke Mehrtens.

See Documentation/SubmittingPatches

The Signed-off-by: tag indicates that the signer was involved in the
development of the patch, or that he/she was in the patch's delivery
path.

I googled a bit and found also this:

http://kerneltrap.org/files/Jeremy/DCO.txt

which gives additional clue about what can be behind SOB.

-- 
Best Regards,
Artem Bityutskiy
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://lists.infradead.org/pipermail/linux-mtd/attachments/20130204/99a76bfb/attachment-0001.sig>