Re: [1.8.0] Provide proper remote ref namespaces
- From
Johan Herland <johan@herland.net>
- Date
- Feb 7, 2011, 10:06 UTC
- Message-ID
- <201102071106.17269.johan@herland.net>
- In-Reply-To
- <AANLkTiksUqVnWeZOm-9XN3BbfVcjc6fWdwPcPJ-PLb88@mail.gmail.com>
On Monday 07 February 2011, Sverre Rabbelier wrote:
Show 12 quoted lines
> On Mon, Feb 7, 2011 at 09:58, Johan Herland <johan@herland.net> wrote: > > This is the same technique we use when talking about branch names: > > On this mailing list, nobody is confused when I refer to 'maint', > > 'master', 'next' and 'pu'. Still, in our own work repos (at least > > in mine), these branches are actually called > > "refs/remotes/origin/<name>" (commonly referred to by their > > shorthands "origin/<name>"). Here we are, juggling the same kind of > > namespaces that I propose for tags, and it seems to work well > > without causing much confusion. > > With the difference that you can't refer to "maint" as just "maint" > unless you've created "refs/heads/maint" iff it is unambiguous.
Except that with 'git checkout', you can:
$ git clone git://git.kernel.org/pub/scm/git/git.git $ cd git/ $ git checkout maint
...Johan
-- Johan Herland, <johan@herland.net> www.herland.net