Thread (16 messages) 16 messages, 3 authors, 2013-05-01

Re: [PATCH v3b 1/3] tipc: cosmetic: clean up comments and break a long line

From: Gerlando Falauto <hidden>
Date: 2013-05-01 17:35:19

Hi,

On 05/01/2013 07:16 PM, David Miller wrote:
From: Gerlando Falauto <redacted>
Date: Wed,  1 May 2013 18:41:17 +0200
quoted
Signed-off-by: Gerlando Falauto <redacted>
---
Changes from v3:
* Added "and break a long line" to the commit message
Changes from v2:
* Split cosmetic (this patch) from functional changes (next patch)
Never resubmit patches by themselves, always resubmit the entire series.
I was just wondering what happens in that case, thank you for the 
explanation, I had no idea.
Because when one patch has problems, I toss the entire series from patchwork,
Is "v3b" good or shall I just use v4 instead?
Do I also need to change the version number (and add "Changes from 
previous version" lines) to the subsequent patches, even though nothing 
has actually changed)? Should have I used a cover letter to begin with?

 > and by resubmitting the entire series again you are also giving me 
important
 > information, you're telling me that the subsequent patches in the series
 > still apply cleanly even though the first one has changed.

That I don't understand. I thought it would be the other way around, 
that's why I resubmitted only the one which changed.
If I resubmit the entire series, how can you tell patches 2 and 3 are 
identical to the previous version I posted?

Last question: Is chain reply OK?

Thanks for your patience,
Gerlando

I've tossed this patch too, resubmit this properly, thanks.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help