Re: [WIP-PATCH 0/2] send-email: refactor the email parser loop
- From
- Samuel GROOT <samuel.groot@grenoble-inp.org>
- Date
- May 29, 2016, 17:21 UTC
- Message-ID
- <7423b133-cec4-e633-f1ef-70ccc6a6cc02@grenoble-inp.org>
- In-Reply-To
- <vpq8tyujkb0.fsf@anie.imag.fr>
On 05/28/2016 05:04 PM, Matthieu Moy wrote:
Show 23 quoted lines
> Eric Wong <e@80x24.org> writes: > >> Samuel GROOT <samuel.groot@grenoble-inp.org> wrote: >> >>> (mbox) Adding cc: A<author@example.com> from line 'Cc: A<author@example.com>, One<one@example.com>' >>> (mbox) Adding cc: One<one@example.com> from line 'Cc: A<author@example.com>, One<one@example.com>' >>> >>> Though `git send-email` now outputs something like: >>> >>> (mbox) Adding cc: A<author@example.com> from line 'Cc: A<author@example.com>' >>> (mbox) Adding cc: One<one@example.com> from line 'Cc: One<one@example.com>' >> I actually like neither, and would prefer something shorter: >> >> (mbox) Adding cc: A <author@example.com> from Cc: header >> (mbox) Adding cc: One <one@example.com> from Cc: header >> (mbox) Adding cc: SoB <SoB@example.com> from Signed-off-by: trailer >> >> That way, there's no redundant addresses in each line and less >> likely to wrap. > > I agree with this. Actually, I'd even say that the current output of > "git send-email" looks sloppy, and internal refactoring may be a good > opportunity to get it cleaner.
I agree.
Should we take what Eric suggested (see below) as standard output?
Show 12 quoted lines
> Since the headers are already shown after those lines, it's > redundant to have the entire line. And we could add > trailers after the headers (with a blank line to delimit): > > # existing header output: > From: F <F@example.com> > Cc: A <author@example.com>, One <one@example.com> > Subject: foo > > # new trailer output > Signed-off-by: SoB <SoB@example.com> > Acked-by: ack <ack@example.com>
And keep "(mbox) Adding ..." lines as error output, or maybe displayable by a new option `--verbose`?