u-boot next: a generic approach for nios2 arch
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest0 of 28 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 28 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [U-Boot] [PATCH 00/28] u-boot next: a generic approach for nios2 arch
Quoted 8 lines · Wolfgang Denk
Dear Peter Tyser,
Quoted 4 lines · In message <[email protected]> you wrote:
When you resubmit, please use the "--no-chain-reply-to" option for git send-email. It will properly thread your patch series to prevent the later patches from creeping off the right side of everyone's email clients.
Quoted 4 lines
No, don't!
Peter, I strongly disagree here. If your mailer cannot handle (long) threads correctly, then this is your local problem.
It is not a local problem, it is a common problem. Some people might claim that us not wanting to see HTML on the mailing list is a local problem with our mail clients, too. :-)
And I'm not entirely sure how you're proposing that a mail client *should* deal with such a thread. It's a tradeoff between displaying less of the subject text, or breaking the display of the thread structure earlier. Either one is going to be worse for certain inputs -- and given that in an actual discussion the subject doesn't often change, I'd rather see more of the thread structure.
Even when they don't go off the right edge, chained patchsets are hard on the eyes IMHO. It's semantically a list, not a (fully unbalanced) tree. I'm used to lists going straight down, not diagonally.
Quoted 3 lines
To me it makes perfect sense that a patch series is threaded - some people forget to number the patches, and quite often patch arrive out of order. It is much easier to have these threded correctly.
So why not insist on people numbering their patches rather than creating a huge reply-to chain?
-Scott