From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 00/28] u-boot next: a generic approach for nios2 arch
Date: Fri, 19 Mar 2010 13:56:56 -0500 [thread overview]
Message-ID: <4BA3C8F8.5090804@freescale.com> (raw)
In-Reply-To: <20100319184018.DAFC45086C@gemini.denx.de>
Wolfgang Denk wrote:
> Dear Peter Tyser,
>
> In message <1269010558.3376.5270.camel@localhost.localdomain> 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.
>
> 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.
> 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
next prev parent reply other threads:[~2010-03-19 18:56 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-19 7:43 [U-Boot] [PATCH 00/28] u-boot next: a generic approach for nios2 arch Thomas Chou
2010-03-19 7:43 ` [U-Boot] [PATCH 01/28] nios2: add nios2-generic board Thomas Chou
2010-03-19 7:43 ` [U-Boot] [PATCH 02/28] cfi flash: add status polling method for amd flash Thomas Chou
2010-03-19 7:43 ` [U-Boot] [PATCH 03/28] serial: move altera uart driver to drivers/serial Thomas Chou
2010-03-19 7:43 ` [U-Boot] [PATCH 04/28] serial: move altera jtaguart " Thomas Chou
2010-03-19 7:43 ` [U-Boot] [PATCH 05/28] serial: move yanu " Thomas Chou
2010-03-19 7:43 ` [U-Boot] [PATCH 06/28] spi: add altera spi controller support Thomas Chou
2010-03-19 7:43 ` [U-Boot] [PATCH 07/28] net: add opencore 10/100 ethernet mac support Thomas Chou
2010-03-19 7:43 ` [U-Boot] [PATCH 08/28] net: add altera triple speeds " Thomas Chou
2010-03-19 7:43 ` [U-Boot] [PATCH 09/28] nios2: change asm-nios2/io.h to compatible with nios2 linux Thomas Chou
2010-03-19 7:43 ` [U-Boot] [PATCH 10/28] nios2: add asm-nios2/errno.h Thomas Chou
2010-03-19 7:43 ` [U-Boot] [PATCH 11/28] nios2: add local_irq_enable/disable to asm-nios2/system.h Thomas Chou
2010-03-19 7:43 ` [U-Boot] [PATCH 12/28] nios2: use bitops from linux-2.6 asm-generic Thomas Chou
2010-03-19 7:43 ` [U-Boot] [PATCH 13/28] nios2: fix __fswab64 link error with asm-nios2/byteorder.h Thomas Chou
2010-03-19 7:43 ` [U-Boot] [PATCH 14/28] nios2: add dma_alloc_coherent with asm-nios2/dma-mapping.h Thomas Chou
2010-03-19 7:43 ` [U-Boot] [PATCH 15/28] nios2: add gpio support with asm-nios2/gpio.h Thomas Chou
2010-03-19 7:43 ` [U-Boot] [PATCH 16/28] nios2: move timer handler from interrupt.c to timer.c Thomas Chou
2010-03-19 7:43 ` [U-Boot] [PATCH 17/28] nios2: define text_base in start.S for linker script Thomas Chou
2010-03-19 7:43 ` [U-Boot] [PATCH 18/28] nios2: pass command line and initrd to linux Thomas Chou
2010-03-19 7:43 ` [U-Boot] [PATCH 19/28] nios2: board init for eth, no flash, nand and mmc Thomas Chou
2010-03-19 7:43 ` [U-Boot] [PATCH 20/28] nios2: fix writel in board/altera/common/epled.c Thomas Chou
2010-03-19 7:43 ` [U-Boot] [PATCH 21/28] nios2: add cf ide init and reset handler Thomas Chou
2010-03-19 7:43 ` [U-Boot] [PATCH 22/28] nios2: add gpio led driver Thomas Chou
2010-03-19 7:43 ` [U-Boot] [PATCH 23/28] nios2: convert ep1c20 board to use cfi flash and spi flash Thomas Chou
2010-03-19 7:43 ` [U-Boot] [PATCH 24/28] nios2: convert ep1s10 board to use cfi flash Thomas Chou
2010-03-19 7:43 ` [U-Boot] [PATCH 25/28] nios2: convert ep1s40 " Thomas Chou
2010-03-19 7:43 ` [U-Boot] [PATCH 26/28] nios2: convert pci5441 " Thomas Chou
2010-03-19 7:43 ` [U-Boot] [PATCH 27/28] nios2: convert pk1c20 board to use cfi flash and spi flash Thomas Chou
2010-03-19 7:43 ` [U-Boot] [PATCH 28/28] nios2: add struct stat support in linux/stat.h Thomas Chou
2010-04-05 5:36 ` [U-Boot] [PATCH 01/28] nios2: add nios2-generic board Ben Warren
2010-04-07 3:19 ` Thomas Chou
2010-04-07 17:23 ` Ben Warren
2010-03-19 14:41 ` [U-Boot] [PATCH 00/28] u-boot next: a generic approach for nios2 arch Thomas Chou
2010-03-19 14:55 ` Peter Tyser
2010-03-19 15:23 ` Thomas Chou
2010-03-19 18:40 ` Wolfgang Denk
2010-03-19 18:56 ` Scott Wood [this message]
2010-03-19 19:59 ` Wolfgang Denk
2010-03-19 21:07 ` Peter Tyser
2010-03-21 20:28 ` Wolfgang Denk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BA3C8F8.5090804@freescale.com \
--to=scottwood@freescale.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox