From: Jeff King <peff@peff.net>
To: "Kirill A. Korinskiy" <catap@catap.ru>
Cc: gitster@pobox.com, git@vger.kernel.org
Subject: Re: [PATCH] Add option -b/--branch to clone for select a new HEAD
Date: Tue, 25 Aug 2009 17:57:26 -0400 [thread overview]
Message-ID: <20090825215726.GA30981@coredump.intra.peff.net> (raw)
In-Reply-To: <1251228467-29638-1-git-send-email-catap@catap.ru>
On Tue, Aug 25, 2009 at 11:27:47PM +0400, Kirill A. Korinskiy wrote:
> +test_expect_success 'clone' '
> +
> + git clone parent clone &&
> + (cd clone && git rev-parse --verify refs/remotes/origin/master)
> +
> +'
> +
> +test_expect_success 'clone -b' '
> +
> + git clone -b two parent clone-b &&
> + (cd clone-b && test $(git rev-parse --verify HEAD) = $(git rev-parse --verify refs/remotes/origin/two))
> +
> +'
OK, I think that second test makes sense (though please wrap the very
long line), but now what is the first one doing? Shouldn't it be:
(cd clone &&
test $(git rev-parse --verify HEAD) = \
$(git rev-parse --verify refs/remotes/origin/master)
)
also?
-Peff
next prev parent reply other threads:[~2009-08-25 21:57 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87praj90n8.wl%catap@catap.ru>
2009-08-25 19:25 ` [PATCH] Add option -b/--branch to clone for select a new HEAD Kirill A. Korinskiy
2009-08-25 19:27 ` Kirill A. Korinskiy
2009-08-25 21:57 ` Jeff King [this message]
2009-08-25 22:42 ` Junio C Hamano
2009-08-25 22:36 ` Björn Steinbrink
[not found] ` <87ljl694fd.wl%catap@catap.ru>
2009-08-26 12:16 ` Björn Steinbrink
2009-08-26 14:46 ` Kirill A. Korinskiy
2009-08-26 15:50 ` Björn Steinbrink
2009-08-26 16:10 ` Jeff King
2009-08-26 16:56 ` Björn Steinbrink
2009-08-26 17:48 ` Jeff King
2009-08-26 19:05 ` Jeff King
2009-08-28 10:31 ` Tor Arne Vestbø
2009-08-28 11:05 ` Martin Langhoff
2009-08-28 12:10 ` Julian Phillips
2009-08-24 20:42 Kirill A. Korinskiy
2009-08-25 1:57 ` Jeff King
2009-08-25 2:13 ` Junio C Hamano
2009-08-25 17:20 ` Kirill A. Korinskiy
2009-08-25 19:00 ` Jeff King
2009-08-25 12:30 ` Kirill A. Korinskiy
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=20090825215726.GA30981@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=catap@catap.ru \
--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).