From: Junio C Hamano <gitster@pobox.com>
To: Johannes Sixt <j6t@kdbg.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 1/3] t3400-rebase: Move detached HEAD check earlier
Date: Mon, 02 Mar 2009 00:03:19 -0800 [thread overview]
Message-ID: <7vmyc45p2w.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <1235902803-32528-1-git-send-email-j6t@kdbg.org> (Johannes Sixt's message of "Sun, 1 Mar 2009 11:20:03 +0100")
Johannes Sixt <j6t@kdbg.org> writes:
> Long story: The test that preceded the one in question tests that a
> rebased commit degrades from a content change with mode change to a
> mere mode change. But on Windows, where we have core.filemode=false,
> the original commit did not record the mode change, and so the rebase
> operation did not rebase anything. This caused the subsequent detached
> HEAD test to fail.
Thanks.
I'll apply it as is since it is very close to the real release, but I
think a more suitable fix would be to make tests less dependent on the
outcome of earlier tests.
prev parent reply other threads:[~2009-03-02 8:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-01 10:20 [PATCH 1/3] t3400-rebase: Move detached HEAD check earlier Johannes Sixt
2009-03-01 11:21 ` Johannes Sixt
2009-03-02 8:03 ` Junio C Hamano [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=7vmyc45p2w.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=j6t@kdbg.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 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).