Re: [PATCH] SubmittingPatches: clarify SOB tag usage when evolving submissions

2012-08-15 Thread Dan Carpenter
I think it would be nice to have another tag for people who fix bugs in the original patch. The Reviewed-by tag implies approval of the whole patch and anyway reviewers don't normally comment unless they see a bug. Maybe something like: Contributor: Your Name So the tags for developers would

Re: [PATCH] SubmittingPatches: clarify SOB tag usage when evolving submissions

2012-08-15 Thread Dan Carpenter
I think it would be nice to have another tag for people who fix bugs in the original patch. The Reviewed-by tag implies approval of the whole patch and anyway reviewers don't normally comment unless they see a bug. Maybe something like: Contributor: Your Name em...@address.com So the tags for

Re: [PATCH] SubmittingPatches: clarify SOB tag usage when evolving submissions

2012-08-09 Thread Ryan Mallon
On 10/08/12 06:51, Luis R. Rodriguez wrote: > From: "Luis R. Rodriguez" > > Initial large code submissions typically are not accepted > on their first patch submission. The developers are > typically given feedback and at times some developers may > even submit changes to the original authors

Re: [PATCH] SubmittingPatches: clarify SOB tag usage when evolving submissions

2012-08-09 Thread Luis R. Rodriguez
On Thu, Aug 9, 2012 at 1:58 PM, Geert Uytterhoeven wrote: > On Thu, Aug 9, 2012 at 10:51 PM, Luis R. Rodriguez > wrote: >> of a second patch submission must supply their own Siged-off-by > > Signed-off-by will send a v2. Luis -- To unsubscribe from this list: send the line "unsubscribe

Re: [PATCH] SubmittingPatches: clarify SOB tag usage when evolving submissions

2012-08-09 Thread Geert Uytterhoeven
On Thu, Aug 9, 2012 at 10:51 PM, Luis R. Rodriguez 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

[PATCH] SubmittingPatches: clarify SOB tag usage when evolving submissions

2012-08-09 Thread Luis R. Rodriguez
From: "Luis R. Rodriguez" Initial large code submissions typically are not accepted on their first patch submission. The developers are typically given feedback and at times some developers may even submit changes to the original authors for integration into their second submission attempt.

[PATCH] SubmittingPatches: clarify SOB tag usage when evolving submissions

2012-08-09 Thread Luis R. Rodriguez
From: Luis R. Rodriguez mcg...@do-not-panic.com Initial large code submissions typically are not accepted on their first patch submission. The developers are typically given feedback and at times some developers may even submit changes to the original authors for integration into their second

Re: [PATCH] SubmittingPatches: clarify SOB tag usage when evolving submissions

2012-08-09 Thread Geert Uytterhoeven
On Thu, Aug 9, 2012 at 10:51 PM, Luis R. Rodriguez mcg...@do-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

Re: [PATCH] SubmittingPatches: clarify SOB tag usage when evolving submissions

2012-08-09 Thread Luis R. Rodriguez
On Thu, Aug 9, 2012 at 1:58 PM, Geert Uytterhoeven ge...@linux-m68k.org wrote: On Thu, Aug 9, 2012 at 10:51 PM, Luis R. Rodriguez mcg...@do-not-panic.com wrote: of a second patch submission must supply their own Siged-off-by Signed-off-by will send a v2. Luis -- To unsubscribe from this

Re: [PATCH] SubmittingPatches: clarify SOB tag usage when evolving submissions

2012-08-09 Thread Ryan Mallon
On 10/08/12 06:51, Luis R. Rodriguez wrote: From: Luis R. Rodriguez mcg...@do-not-panic.com Initial large code submissions typically are not accepted on their first patch submission. The developers are typically given feedback and at times some developers may even submit changes to the