From: Kyle Meyer <kyle@kyleam•com>
To: Junio C Hamano <gitster@pobox•com>
Cc: git@vger•kernel.org
Subject: Re: name-rev: anchor pattern without --exclude?
Date: Thu, 06 Jul 2017 13:23:02 -0400 [thread overview]
Message-ID: <87h8yptr7t.fsf@kyleam.com> (raw)
In-Reply-To: <xmqqfue9fqfe.fsf@gitster.mtv.corp.google.com>
Junio C Hamano <gitster@pobox•com> writes:
> Kyle Meyer <kyle@kyleam•com> writes:
>
>> [*] A bit more information on why I'm trying to do this: In Magit, we
>> have a work-in-progress feature that takes "snapshots" of changes
>> before they are committed. These snapshots are stored as
>> "refs/wip/{wtree,index}/<full refname>".
>>
>> We want to use name-rev to map a commit to a name in "refs/heads/",
>> ignoring these snapshot refs.
>
> What is the <full refname> in the above supposed to represent?
It's the current branch, as returned by "git symbolic-ref HEAD".
> When a user sees two refs "refs/wip/{wtree,index}/<full refname>",
> does it mean: "These two represent a snapshot for changes while the
> user was working on this branch"?
Yes.
> Isn't name-rev a wrong tool to find that information?
Sorry for the confusion. We're using "symbolic-ref HEAD" to get the
above information. I was just trying to explain why we're dealing with
ref names that contain a "refs/heads" substring (like
refs/wip/wtree/refs/heads/master in the example I gave).
> What is the answer desired by your application when two or more
> branches point at the same commit you are interested in? Pick one at
> random? An error saying it cannot decide where to place the snapshot?
Our use of name-rev is just to get a friendly name for a hash. If two
branches point to the same commit, we're fine with whatever decision
"git name-rev" makes; we just want to limit it to refs in the
"refs/heads/" namespace.
--
Kyle
next prev parent reply other threads:[~2017-07-06 17:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-06 16:53 name-rev: anchor pattern without --exclude? Kyle Meyer
2017-07-06 17:03 ` Junio C Hamano
2017-07-06 17:23 ` Kyle Meyer [this message]
2017-07-06 18:02 ` Bryan Turner
2017-07-06 18:26 ` Kyle Meyer
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=87h8yptr7t.fsf@kyleam.com \
--to=kyle@kyleam$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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