[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMuHMdUd5x04KyyKa84J3PDB2xPj70xZLezwMJn1J=jwmzcnnA@mail.gmail.com>
Date: Thu, 9 Aug 2012 22:58:27 +0200
From: Geert Uytterhoeven <geert@...ux-m68k.org>
To: "Luis R. Rodriguez" <mcgrof@...not-panic.com>
Cc: torvalds@...ux-foundation.org, rdunlap@...otime.net, tytso@....edu,
alan@...rguk.ukuu.org.uk, davem@...emloft.net,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] SubmittingPatches: clarify SOB tag usage when evolving submissions
On Thu, Aug 9, 2012 at 10:51 PM, Luis R. Rodriguez
<mcgrof@...not-panic.com> wrote:
> of a second patch submission must supply their own Siged-off-by
Signed-off-by
> --- a/Documentation/SubmittingPatches
> +++ b/Documentation/SubmittingPatches
> @@ -366,6 +366,21 @@ and protect the submitter from complaints. Note that under no circumstances
> can you change the author's identity (the From header), as it is the one
> which appears in the changelog.
>
> +If you are submitting a large change (for example a new driver) at times
> +you may be asked to make quite a lot of modifications prior to getting
> +your change accepted. At times you may even receive patches from developers
> +who not only wish to tell you what you should change to get your changes
> +upstream but actually send you patches. If those patches were made publicly
> +and they do contain a Singed-off-by tag you are not expected to provide
Signed-off-by
> +their own Singed-off-by tag on the second iteration of the patch so long
idem
> +as there is a public record somewhere that can be used to show the
> +contributor had sent their changes with their own Singed-off-by tag.
ditto
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists