From: Jakub Narebski <jnareb@gmail.com>
To: "John Dlugosz" <JDlugosz@TradeStation.com>
Cc: <git@vger.kernel.org>
Subject: Re: remote branches, and branch names in general
Date: Mon, 02 Mar 2009 16:38:42 -0800 (PST) [thread overview]
Message-ID: <m3vdqrtp84.fsf@localhost.localdomain> (raw)
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.
>
> 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
next prev parent reply other threads:[~2009-03-03 0:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-02 20:46 remote branches, and branch names in general John Dlugosz
2009-03-03 0:38 ` Jakub Narebski [this message]
2009-03-03 4:16 ` Jeff King
2009-03-03 8:58 ` Markus Heidelberg
2009-03-03 9:05 ` Jeff King
2009-03-03 15:52 ` John Dlugosz
2009-03-03 16:11 ` Jeff King
2009-03-03 19:32 ` Jay Soffian
2009-03-04 10:29 ` Jeff King
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=m3vdqrtp84.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=JDlugosz@TradeStation.com \
--cc=git@vger.kernel.org \
/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