From: Christian Couder <christian.couder@gmail.com>
To: git <git@vger.kernel.org>
Cc: Junio C Hamano <gitster@pobox.com>,
Christian Couder <chriscool@tuxfamily.org>
Subject: Re: [PATCH v2] builtin/apply: exit when parse_binary() fails
Date: Thu, 17 Mar 2016 10:34:25 +0100 [thread overview]
Message-ID: <CAP8UFD2NgSfVVZrshimM+=7dFmhjqGmUVsTymgoQOXvhegr_1g@mail.gmail.com> (raw)
In-Reply-To: <1458206614-2898-1-git-send-email-chriscool@tuxfamily.org>
On Thu, Mar 17, 2016 at 10:23 AM, Christian Couder
<christian.couder@gmail.com> wrote:
> In parse_binary() there is:
...
Of course just after sending this I realized that I should probably
change the title of the patch to something like "builtin/apply: handle
parse_binary() failure".
I will resend a v3 with the above change later...
prev parent reply other threads:[~2016-03-17 9:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-17 9:23 [PATCH v2] builtin/apply: exit when parse_binary() fails Christian Couder
2016-03-17 9:34 ` Christian Couder [this message]
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='CAP8UFD2NgSfVVZrshimM+=7dFmhjqGmUVsTymgoQOXvhegr_1g@mail.gmail.com' \
--to=christian.couder@gmail.com \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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;
as well as URLs for NNTP newsgroup(s).