Re: remote branches, and branch names in general

From: Jakub Narebski <jnareb@gmail.com>
Date: Mar 3, 2009, 00:38 UTC
Message-ID: <m3vdqrtp84.fsf@localhost.localdomain>
In-Reply-To: <450196A1AAAE4B42A00A8B27A59278E709F07398@EXCHANGE.trad.tradestation.com>

"John Dlugosz" <JDlugosz@TradeStation.com> writes:

> I see the remote branches with names of the form remotes/pub/name where
> pub is the nickname of the place I pull from.  To specify such branches,
> must I always spell it out with the leading "remotes/", or can that be
> shorted or implied somehow?

You usually can omit "remotes/" prefix, and just use "<remote>/<branch>" (or even "<remote>" for "<remote>/HEAD"). You need it only if there is need for disambiguation.

Show 5 quoted lines

> 
> Meanwhile, I see that branch names can be hierarchical, as I found out
> when I accidently created a branch called "pub/xxx".  So I'm wondering
> about the usefulness of using that for organizing topic branches based
> on assigned tasks organization and the person owning that branch.

Junio uses branches like 'fc/parseopt-config' (initials + feature) in git development...

-- 
Jakub Narebski
Poland
ShadeHawk on #git