From: Jeff King <peff@peff.net>
To: Stanislav Kolotinskiy <stanislav@assembla.com>
Cc: Dave Borowitz <dborowitz@google.com>, git@vger.kernel.org
Subject: Re: [PATCH] git-send-pack: Fix --all option when used with directory
Date: Wed, 23 Mar 2016 17:30:34 -0400 [thread overview]
Message-ID: <20160323213034.GB19920@sigill.intra.peff.net> (raw)
In-Reply-To: <20160323212213.GA19920@sigill.intra.peff.net>
On Wed, Mar 23, 2016 at 05:22:13PM -0400, Jeff King wrote:
> > diff --git a/t/t9904-send-pack-all.sh b/t/t9904-send-pack-all.sh
>
> The tests are roughly grouped by functionality. send-pack tests are in
> the t540x range, and this should probably go there. Though I also
> suspect it could easily be added to the end of an existing test script,
> which is preferable.
>
> > +test_expect_success setup '
>
> This setup seems a bit more complicated than it needs to be. It's nice
> to keep tests as simple as possible, so a reader can understand exactly
> what is being tested.
>
> Here are a few things I think we can simplify:
> [...]
So I think we could replace your t9904 with something like this:
diff --git a/t/t5400-send-pack.sh b/t/t5400-send-pack.sh
index 04cea97..305ca7a 100755
--- a/t/t5400-send-pack.sh
+++ b/t/t5400-send-pack.sh
@@ -128,6 +128,18 @@ test_expect_success 'denyNonFastforwards trumps --force' '
test "$victim_orig" = "$victim_head"
'
+test_expect_success 'send-pack --all sends all branches' '
+ # make sure we have at least 2 branches with different
+ # values, just to be thorough
+ git branch other-branch HEAD^ &&
+
+ git init --bare all.git &&
+ git send-pack --all all.git &&
+ git for-each-ref refs/heads >expect &&
+ git -C all.git for-each-ref refs/heads >actual &&
+ test_cmp expect actual
+'
+
test_expect_success 'push --all excludes remote-tracking hierarchy' '
mkdir parent &&
(
next prev parent reply other threads:[~2016-03-23 21:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-23 16:24 [PATCH] git-send-pack: Fix --all option when used with directory Stanislav Kolotinskiy
2016-03-23 21:22 ` Jeff King
2016-03-23 21:30 ` Jeff King [this message]
2016-03-24 13:57 ` Stanislav Kolotinskiy
2016-03-24 17:37 ` Jeff King
2016-03-24 17:49 ` Stanislav Kolotinskiy
2016-03-24 16:11 ` Junio C Hamano
2016-03-24 17:47 ` Stanislav Kolotinskiy
2016-03-24 18:02 ` Jeff King
2016-04-01 10:42 ` Stanislav Kolotinskiy
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=20160323213034.GB19920@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=dborowitz@google.com \
--cc=git@vger.kernel.org \
--cc=stanislav@assembla.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).