From: Matt Kraai <kraai@ftbfs.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Create .dotest-merge after validating options.
Date: Thu, 27 Sep 2007 07:03:13 -0700 [thread overview]
Message-ID: <20070927140312.GA4499@ftbfs.org> (raw)
In-Reply-To: <7vfy10woqi.fsf@gitster.siamese.dyndns.org>
On Thu, Sep 27, 2007 at 12:29:09AM -0700, Junio C Hamano wrote:
> Matt Kraai <kraai@ftbfs.org> writes:
>
> > Creating .dotest-merge before validating the options prevents both
> > --continue and --interactive from working if the options are invalid,
> > so only create it after validating the options.
>
> Thanks. Will apply with a minor fixup. Next time, please make
> sure the testsuite passes before submitting.
Will do, thanks.
--
Matt
prev parent reply other threads:[~2007-09-27 14:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-26 1:30 [PATCH] Create .dotest-merge after validating options Matt Kraai
2007-09-26 1:38 ` Johannes Schindelin
2007-09-27 7:29 ` Junio C Hamano
2007-09-27 14:03 ` Matt Kraai [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=20070927140312.GA4499@ftbfs.org \
--to=kraai@ftbfs.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).