From: Johannes Sixt <j.sixt@viscovery.net>
To: Jeff King <peff@peff.net>
Cc: Jay Soffian <jaysoffian@gmail.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: t5505-remote fails on Windows
Date: Thu, 19 Mar 2009 08:20:18 +0100 [thread overview]
Message-ID: <49C1F232.2090009@viscovery.net> (raw)
In-Reply-To: <20090319044313.GA341@coredump.intra.peff.net>
Jeff King schrieb:
> I didn't look closely enough at your issue, which is one
> ref pushing to two different places. For that, the sort needs to take
> into account the util field, which holds the destination.
>
> The patch below probably fixes it, but as I can't actually reproduce
> here, it is largely untested.
Your patch fixes it. The following change to the test case would be a good
addition; it protects later tests from failures in earlier tests.
-- Hannes
diff --git a/t/t5505-remote.sh b/t/t5505-remote.sh
index 5ec668d..13f32b8 100755
--- a/t/t5505-remote.sh
+++ b/t/t5505-remote.sh
@@ -160,7 +160,7 @@ cat > test/expect << EOF
master pushes to another (up to date)
EOF
-test_expect_success 'show' '
+test_expect_success 'more setup for show' '
(cd test &&
git config --add remote.origin.fetch refs/heads/master:refs/heads/upstream &&
git fetch &&
@@ -183,12 +183,20 @@ test_expect_success 'show' '
git config --add remote.origin.push refs/heads/master:refs/heads/upstream &&
git config --add remote.origin.push +refs/tags/lastbackup &&
git config --add remote.two.push +refs/heads/ahead:refs/heads/master &&
- git config --add remote.two.push refs/heads/master:refs/heads/another &&
+ git config --add remote.two.push refs/heads/master:refs/heads/another)
+'
+
+test_expect_success 'show' '
+ (cd test &&
git remote show origin two > output &&
- git branch -d rebase octopus &&
test_cmp expect output)
'
+test_expect_success 'more setup for show -n' '
+ (cd test &&
+ git branch -d rebase octopus)
+'
+
cat > test/expect << EOF
* remote origin
URL: $(pwd)/one
next prev parent reply other threads:[~2009-03-19 7:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-18 11:42 t5505-remote fails on Windows Johannes Sixt
2009-03-19 4:18 ` Jeff King
2009-03-19 4:43 ` Jeff King
2009-03-19 4:56 ` Jay Soffian
2009-03-19 5:03 ` Jeff King
2009-03-19 7:20 ` Johannes Sixt [this message]
2009-03-19 20:04 ` Jeff King
2009-03-19 10:36 ` Johannes Schindelin
2009-03-19 11:02 ` Junio C Hamano
2009-03-19 15:00 ` Jay Soffian
2009-03-19 20:03 ` Jeff King
2009-03-19 23:15 ` Johannes Schindelin
2009-03-22 8:59 ` [PATCH] remote: improve sorting of "configure for git push" list Jeff King
2009-03-22 14:47 ` Jay Soffian
2009-03-22 21:58 ` Junio C Hamano
2009-03-23 7:56 ` Johannes Sixt
2009-03-23 8:09 ` Junio C Hamano
2009-03-19 19:52 ` t5505-remote fails on Windows Jeff King
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=49C1F232.2090009@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=git@vger.kernel.org \
--cc=jaysoffian@gmail.com \
--cc=peff@peff.net \
/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).