From: Bruce Stephens <bruce.stephens@isode•com>
To: Junio C Hamano <gitster@pobox•com>
Cc: Michael J Gruber <git@drmicha•warpmail.net>, git@vger•kernel.org
Subject: Re: Change in "git checkout" behaviour between 1.6.0.2 and 1.6.0.3
Date: Wed, 12 Nov 2008 19:44:47 +0000 [thread overview]
Message-ID: <80od0ksp8w.fsf@tiny.isode.net> (raw)
In-Reply-To: <7vprl0oiw6.fsf@gitster.siamese.dyndns.org> (Junio C. Hamano's message of "Wed\, 12 Nov 2008 11\:15\:37 -0800")
Junio C Hamano <gitster@pobox•com> writes:
[...]
> Yeah, it was meant to allow:
>
> git clone -n $there $here
> cd $here
> git checkout
>
> and was not taking care of the case to switch branches when the initial
> checkout is made.
That specific sequence does work. I guess that's why I hadn't noticed
the issue for so long (I guess git's test suite has some tests using
"clone -n", and perhaps they're of that form).
> Perhaps this would help.
Works for me.
[...]
next prev parent reply other threads:[~2008-11-12 19:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-12 14:36 Change in "git checkout" behaviour between 1.6.0.2 and 1.6.0.3 Bruce Stephens
2008-11-12 17:32 ` Michael J Gruber
2008-11-12 17:44 ` Bruce Stephens
2008-11-12 19:15 ` Junio C Hamano
2008-11-12 19:44 ` Bruce Stephens [this message]
2008-11-12 19:52 ` Re* " Junio C Hamano
2008-11-12 17:40 ` Bruce Stephens
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=80od0ksp8w.fsf@tiny.isode.net \
--to=bruce.stephens@isode$(echo .)com \
--cc=git@drmicha$(echo .)warpmail.net \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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