From: Junio C Hamano <gitster@pobox.com>
To: Sergey Organov <sorganov@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Annoyance wrt ref@{1} and reflog expiry
Date: Fri, 19 Jun 2020 13:44:37 -0700 [thread overview]
Message-ID: <xmqqsgeqg4zu.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <xmqqwo42g5ld.fsf@gitster.c.googlers.com> (Junio C. Hamano's message of "Fri, 19 Jun 2020 13:31:42 -0700")
Junio C Hamano <gitster@pobox.com> writes:
> Or we could change the lookup side to use the value of the ref
> itself when asked for @{0}, and use the "old" side of the only entry
> when asked for @{1}. That way, we do not need to play games with an
> artificial entry at all, which may be a better solution.
In other words, looking up @{0} will be the only special case. A
natural consequence of the above way to look up @{1} is to look at
the old side of (N-1)th entry in the reflog for @{N}.
I am starting to like this idea, but I am not sure how tricky the
actual implementation would be.
prev parent reply other threads:[~2020-06-19 20:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-19 18:03 Annoyance wrt ref@{1} and reflog expiry Junio C Hamano
2020-06-19 18:14 ` Sergey Organov
2020-06-19 20:31 ` Junio C Hamano
2020-06-19 20:36 ` Mike Hommey
2020-06-19 21:49 ` Junio C Hamano
2020-06-19 20:44 ` Junio C Hamano [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=xmqqsgeqg4zu.fsf@gitster.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=sorganov@gmail.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 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).