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, Tom RUSSELLO <tom.russello@grenoble-inp•org>
Subject: Re: [WIP-PATCH 1/2] send-email: create email parser subroutine
Date: Sun, 29 May 2016 19:53:26 +0200 [thread overview]
Message-ID: <vpqpos4hht5.fsf@anie.imag.fr> (raw)
In-Reply-To: <8904f487-985c-bd2d-a8d1-4a712c6ef558@grenoble-inp.org> (Samuel GROOT's message of "Sun, 29 May 2016 19:15:10 +0200")
Samuel GROOT <samuel.groot@grenoble-inp•org> writes:
> So should we merge parse_email and parse_header in one unique
> subroutine?
At least on the user (i.e. caller of the API) side, one function is
probably enough.
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
next prev parent reply other threads:[~2016-05-29 17:53 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 [this message]
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
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=vpqpos4hht5.fsf@anie.imag.fr \
--to=matthieu.moy@grenoble-inp$(echo .)fr \
--cc=aaron@schrab$(echo .)com \
--cc=e@80x24$(echo .)org \
--cc=erwan.mathoniere@grenoble-inp$(echo .)org \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=jordan.de-gea@grenoble-inp$(echo .)org \
--cc=samuel.groot@grenoble-inp$(echo .)org \
--cc=tom.russello@grenoble-inp$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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