From: Jesse Hopkins <jesse.hops@gmail.com>
To: John Keeping <john@keeping.me.uk>
Cc: git@vger.kernel.org
Subject: Re: determine name of tag used for checkout when multiple tags exist?
Date: Sat, 5 Sep 2015 08:23:03 -0600 [thread overview]
Message-ID: <CAL3By-9e2ZjShFxMKoLfc_q0LFvB51m15Z8Ydp8b8fGNdcUp_A@mail.gmail.com> (raw)
In-Reply-To: <20150904111915.GB27660@serenity.lan>
On Fri, Sep 4, 2015 at 5:19 AM, John Keeping <john@keeping.me.uk> wrote:
> I think it would be a reasonable enhancement to include the branch name
> in the reflog message if "-b" is given to "git clone", but I'm not aware
> of any (formal) policy on the format of reflog messages so relying on
> any particular message may not be 100% reliable across Git upgrades.
Thanks for posting my dropped message. Apparently the gmail Android
app doesn't do plain text. I understand that parsing the reflog
message may not be future-proof, but I'm going to go for it. I think
that will be more reliable than trying to track the tag name
externally. Having the reflog message show up for a "-b" clone would
be helpful, but it will be easy enough for me to clone HEAD, then
immediately checkout the tag of interest. Thanks again for the
suggestion, would've never thought use the reflog.
prev parent reply other threads:[~2015-09-05 14:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-04 2:53 determine name of tag used for checkout when multiple tags exist? Jesse Hopkins
2015-09-04 4:59 ` Jacob Keller
2015-09-04 7:54 ` John Keeping
[not found] ` <CAL3By-8ieAQPyR9k63_T5Fa9ZnAY8qSNZUpr_=fxebEcN=Zi7g@mail.gmail.com>
[not found] ` <CAL3By-8cgAz1Jau3NO0kkHAVwvy3hPMMUn=xwUtY78TE5WE9vw@mail.gmail.com>
2015-09-04 11:19 ` John Keeping
2015-09-05 14:23 ` Jesse Hopkins [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=CAL3By-9e2ZjShFxMKoLfc_q0LFvB51m15Z8Ydp8b8fGNdcUp_A@mail.gmail.com \
--to=jesse.hops@gmail.com \
--cc=git@vger.kernel.org \
--cc=john@keeping.me.uk \
/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).