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

2012-08-15 Thread Luis R. Rodriguez
On Sun, Aug 12, 2012 at 4:49 PM, Rob Landley wrote: > The analogy I made was with a magazine editor, fighting off sturgeon's > law in the slush pile, cherry-picking a few submissions to polish up and > include in the next issue of the magazine. In this context, a > personalized rejection letter

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

2012-08-15 Thread Luis R. Rodriguez
On Sun, Aug 12, 2012 at 4:49 PM, Rob Landley r...@landley.net wrote: The analogy I made was with a magazine editor, fighting off sturgeon's law in the slush pile, cherry-picking a few submissions to polish up and include in the next issue of the magazine. In this context, a personalized

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

2012-08-12 Thread Rob Landley
On 08/10/2012 12:38 PM, Randy Dunlap wrote: > On 08/09/2012 02:48 PM, 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

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

2012-08-12 Thread Rob Landley
On 08/10/2012 12:38 PM, Randy Dunlap wrote: On 08/09/2012 02:48 PM, 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

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

2012-08-10 Thread Randy Dunlap
On 08/09/2012 02:48 PM, 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

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

2012-08-10 Thread Randy Dunlap
On 08/09/2012 02:48 PM, 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

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

2012-08-09 Thread Joe Perches
On Thu, 2012-08-09 at 14:48 -0700, 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

[PATCH v2] 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 v2] 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 v2] SubmittingPatches: clarify SOB tag usage when evolving submissions

2012-08-09 Thread Joe Perches
On Thu, 2012-08-09 at 14:48 -0700, 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