From: Felipe Contreras <felipe.contreras@gmail.com>
To: Martin <me@mfriebe.de>, git@vger.kernel.org
Subject: RE: git checkout -b refs/master origin/master
Date: Fri, 09 Jul 2021 09:56:27 -0500 [thread overview]
Message-ID: <60e8639b87a83_226420859@natae.notmuch> (raw)
In-Reply-To: <71d3662c-411b-88aa-5cfc-b2f86a067507@mfriebe.de>
Martin wrote:
> Especially the effect on
> git for-each-ref --format="ref=%(refname:lstrip=-1)"
> master
It's probably better to do refname:lstrip=2.
> You only get part of the branch name.
> Because "lstrip" does not distinguish between the / as separator in the
> refs, and the "/" as part of the name.
That shouldn't matter. I use 'fc/area/topic' as names of my branches,
and I know Junio uses similar names: '<contributor>/topic'.
--
Felipe Contreras
prev parent reply other threads:[~2021-07-09 14:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-09 12:40 git checkout -b refs/master origin/master Martin
2021-07-09 14:56 ` Felipe Contreras [this message]
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=60e8639b87a83_226420859@natae.notmuch \
--to=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=me@mfriebe.de \
/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;
as well as URLs for NNTP newsgroup(s).