From: Junio C Hamano <gitster@pobox.com>
To: Kyle Meyer <kyle@kyleam.com>
Cc: git@vger.kernel.org
Subject: Re: name-rev: anchor pattern without --exclude?
Date: Thu, 06 Jul 2017 10:03:49 -0700 [thread overview]
Message-ID: <xmqqfue9fqfe.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <87k23ltsl6.fsf@kyleam.com> (Kyle Meyer's message of "Thu, 06 Jul 2017 12:53:25 -0400")
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? 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"?
Isn't name-rev a wrong tool to find that information? 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?
I am wondering if you are looking for "symbolic-ref HEAD".
next prev parent reply other threads:[~2017-07-06 17:04 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 [this message]
2017-07-06 17:23 ` Kyle Meyer
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=xmqqfue9fqfe.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=kyle@kyleam.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.