From: Junio C Hamano <gitster@pobox.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: Han-Wen Nienhuys <hanwen@google.com>, git <git@vger.kernel.org>,
Jeff King <peff@peff.net>, Martin Fick <mfick@codeaurora.org>
Subject: Re: Distinguishing FF vs non-FF updates in the reflog?
Date: Mon, 22 Mar 2021 11:36:10 -0700 [thread overview]
Message-ID: <xmqqh7l36nol.fsf@gitster.g> (raw)
In-Reply-To: <878s6fqgze.fsf@evledraar.gmail.com> ("Ævar Arnfjörð Bjarmason"'s message of "Mon, 22 Mar 2021 17:40:37 +0100")
Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:
>> I'm confused.
>>
>> rows[0][1] == "0f3a981cbd5be5f97e9504ab770cd88f988fe820"
>> rows[1][0] == "0f3a981cbd5be5f97e9504ab770cd88f988fe820"
>>
>> they are the same. I don't understand your argument.
>
> Sorry, I mean same = ff update, not the same = non-ff. So I flipped
> those around in describing it.
I am confused too. Are you tacking something else, a gap in a run
of reflog entries? If I go from commit A to B to C, the first log
entry would record the transtion from A->B, and the second entry
would record the transition from B->C, and the lack of gap does not
say anything about the relationship between A and B, or B and C. A
can be, and does not have to be, an ancestor of B, and B can be, and
does not have to be, an ancestor of C. Hopping from A to B to C would
leave the same pair of reflog records and I do not think you can tell
the reachability among A and B and C from them.
prev parent reply other threads:[~2021-03-22 18:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-17 20:06 Distinguishing FF vs non-FF updates in the reflog? Han-Wen Nienhuys
2021-03-17 21:21 ` Martin Fick
2021-03-18 8:58 ` Han-Wen Nienhuys
2021-03-18 19:35 ` Jeff King
2021-03-18 22:24 ` Martin Fick
2021-03-22 12:31 ` Han-Wen Nienhuys
2021-03-22 17:45 ` Martin Fick
2021-03-18 22:31 ` Martin Fick
2021-03-18 22:54 ` Jeff King
2021-03-18 19:47 ` Jeff King
2021-03-22 14:40 ` Han-Wen Nienhuys
2021-03-26 7:43 ` Jeff King
2021-03-22 13:26 ` Ævar Arnfjörð Bjarmason
2021-03-22 14:59 ` Han-Wen Nienhuys
2021-03-22 15:39 ` Ævar Arnfjörð Bjarmason
2021-03-22 15:56 ` Han-Wen Nienhuys
2021-03-22 16:40 ` Ævar Arnfjörð Bjarmason
2021-03-22 17:12 ` Han-Wen Nienhuys
2021-03-22 18:36 ` 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqh7l36nol.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=hanwen@google.com \
--cc=mfick@codeaurora.org \
--cc=peff@peff.net \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).