From: Junio C Hamano <gitster@pobox.com>
Date: Thu, 12 Mar 2009 18:31:05 GMT
Subject: Re: git checkout -b origin/mybranch origin/mybranch
Message-ID: <7vbps6lhjq.fsf@gitster.siamese.dyndns.org>
In-Reply-To: <43d8ce650903120618h79686207vaa478c54f34e26f8@mail.gmail.com>

John Tapsell <johnflux@gmail.com> writes:

> I'm saying that:
>
> git checkout -b origin/mybranch  origin/mybranch
>
> Is probably a mistake by the user.  We should warn the user and point
> them in the right direction.

Given Finn Arne Gangstad's use case in a nearby thread, I do not think you
can so easily declare that it is a mistake by the user.

We have traditionally encouraged people to track remote origin/<name> with
matching local <name>, but in a workflow that interact with multiple
remotes, one obvious way to map would be to track remote origin/<name>
with local origin/<name> branch.  You can say remotes/origin/<name> when
you mean the remote tracking one, and say heads/origin/<name> when you
mean the local one, in order to disambiguate in such a setting.