From: Mike Hommey <mh@glandium.org>
To: git@vger.kernel.org, gitster@pobox.com
Subject: Re: [PATCH] t3407-rebase-abort.sh: Enhance existing tests, and add test for rebase --merge
Date: Sat, 1 Mar 2008 12:14:14 +0100 [thread overview]
Message-ID: <20080301111414.GA3112@glandium.org> (raw)
In-Reply-To: <1204369933-3040-1-git-send-email-mh@glandium.org>
On Sat, Mar 01, 2008 at 12:12:13PM +0100, Mike Hommey wrote:
> Removing .dotest should actually not be needed, so just test the directory
> don't exist after --abort, but exists after starting the rebase.
>
> Also, execute the same tests with rebase --merge, which uses a different code
> path.
>
> Signed-off-by: Mike Hommey <mh@glandium.org>
Should have been as a reply to
1204367534-28204-1-git-send-email-mh@glandium.org. Bad copy/paste...
Anyways, this is against your (Junio's) changes.
Mike
prev parent reply other threads:[~2008-03-01 11:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Signed-off-by: Mike Hommey <mh@glandium.org>
2008-03-01 11:12 ` [PATCH] t3407-rebase-abort.sh: Enhance existing tests, and add test for rebase --merge Mike Hommey
2008-03-01 11:14 ` Mike Hommey [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=20080301111414.GA3112@glandium.org \
--to=mh@glandium.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).