From: Derrick Stolee <stolee@gmail.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Junio C Hamano" <gitster@pobox.com>
Cc: wuzhouhui <wuzhouhui14@mails.ucas.ac.cn>, git@vger.kernel.org
Subject: Re: How to get next commit that just after a specified commit
Date: Mon, 18 Feb 2019 14:41:55 -0500 [thread overview]
Message-ID: <8f4bc4cf-cfe4-ddf5-cee3-294ebc5fc88c@gmail.com> (raw)
In-Reply-To: <87ef8bjrqv.fsf@evledraar.gmail.com>
On 2/13/2019 4:36 PM, Ævar Arnfjörð Bjarmason wrote:
>
> On Wed, Feb 13 2019, Junio C Hamano wrote:
>
>> Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:
>
> Their point in comparing it to git is that there's nothing intuitive in
> the UI that exposes this information for the *current* graph, whereas in
> fossil this is a built-in command:
> https://fossil-scm.org/xfer/help/descendants
>
> Perhaps this information is cheaper to extract these days with the
> commit graph and we could expose it somehow?
I believe the recent changes (collected in commit-reach.c) that improve
'git branch --contains' or 'git tag --contains' are important in helping
this descendants list. There is likely more work to be done to show this
list in a rev-list call.
Thanks,
-Stolee
next prev parent reply other threads:[~2019-02-18 19:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-13 9:08 How to get next commit that just after a specified commit wuzhouhui
2019-02-13 9:49 ` Ævar Arnfjörð Bjarmason
2019-02-13 21:12 ` Junio C Hamano
2019-02-13 21:36 ` Ævar Arnfjörð Bjarmason
2019-02-18 19:41 ` Derrick Stolee [this message]
2019-02-15 10:58 ` Philip Oakley
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=8f4bc4cf-cfe4-ddf5-cee3-294ebc5fc88c@gmail.com \
--to=stolee@gmail.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=wuzhouhui14@mails.ucas.ac.cn \
/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).