From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: Samuel GROOT <samuel.groot@grenoble-inp.org>
Cc: Eric Wong <e@80x24.org>,
git@vger.kernel.org, erwan.mathoniere@grenoble-inp.org,
jordan.de-gea@grenoble-inp.org, gitster@pobox.com,
aaron@schrab.com
Subject: Re: [WIP-PATCH 0/2] send-email: refactor the email parser loop
Date: Mon, 30 May 2016 16:20:45 +0200 [thread overview]
Message-ID: <vpqfuszaapu.fsf@anie.imag.fr> (raw)
In-Reply-To: <0abbc11b-5741-ee2e-292c-245c2b974f8e@grenoble-inp.org> (Samuel GROOT's message of "Mon, 30 May 2016 16:01:29 +0200")
Samuel GROOT <samuel.groot@grenoble-inp.org> writes:
> (mbox) prefix was introduced by Ryan Anderson in 2005 (can't find the
> exact commit though), in opposition with the (non-mbox) format ("lots
> of email") that was used before.
That is actually from the original commit introducing send-email:
83b2443 ([PATCH] Add git-send-email-script - tool to send emails from
git-format-patch-script, 2005-07-31), i.e. ~3 month after Git was born.
At that time, user-friendlyness was not really a priority ;-).
> Is the "lots of email" format still used?
AFAICT, it was initially supported for backward compatibility, and then
no one removed it, but I wouldn't be surprised if no one actually used
it.
I vaguely remember a message from Ryan Anderson being surprised to see
the old format still supported, but I can't find it in the archives.
In any case:
- git log --grep 'lots of email' => shows only 83b2443
- git log -S'lots of email' => likewise
- git grep 'lots of email' => just one answer in a comment
I'm not sure the feature is even tested.
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
next prev parent reply other threads:[~2016-05-30 14:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-27 14:01 [WIP-PATCH 0/2] send-email: refactor the email parser loop Samuel GROOT
2016-05-27 14:01 ` [WIP-PATCH 1/2] send-email: create email parser subroutine Samuel GROOT
2016-05-28 15:22 ` Matthieu Moy
2016-05-28 23:33 ` Eric Wong
2016-05-29 17:15 ` Samuel GROOT
2016-05-29 17:53 ` Matthieu Moy
2016-05-30 13:28 ` Samuel GROOT
2016-06-02 16:57 ` Samuel GROOT
2016-06-02 19:58 ` Eric Wong
2016-05-27 14:01 ` [WIP-PATCH 2/2] send-email: use refactored subroutine to parse patches Samuel GROOT
2016-05-27 20:14 ` [WIP-PATCH 0/2] send-email: refactor the email parser loop Eric Wong
2016-05-28 15:04 ` Matthieu Moy
2016-05-29 17:21 ` Samuel GROOT
2016-05-29 18:05 ` Matthieu Moy
2016-05-30 14:01 ` Samuel GROOT
2016-05-30 14:20 ` Matthieu Moy [this message]
2016-05-30 18:28 ` Samuel GROOT
2016-05-30 19:29 ` Matthieu Moy
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=vpqfuszaapu.fsf@anie.imag.fr \
--to=matthieu.moy@grenoble-inp.fr \
--cc=aaron@schrab.com \
--cc=e@80x24.org \
--cc=erwan.mathoniere@grenoble-inp.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jordan.de-gea@grenoble-inp.org \
--cc=samuel.groot@grenoble-inp.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.