git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: How to get next commit that just after a specified commit

From
Derrick Stolee <stolee@gmail.com>
Date
Feb 18, 2019, 19:41 UTC
Message-ID
<8f4bc4cf-cfe4-ddf5-cee3-294ebc5fc88c@gmail.com>
In-Reply-To
<87ef8bjrqv.fsf@evledraar.gmail.com>
On 2/13/2019 4:36 PM, Ævar Arnfjörð Bjarmason wrote:
Show 12 quoted lines
> 
> 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

Previous: Ævar Arnfjörð BjarmasonNext: Philip Oakley
Message 5 of 6 in “How to get next commit that just after a specified commit”
  1. wuzhouhuiFeb 13, 2019
  2. Ævar Arnfjörð BjarmasonFeb 13, 2019
  3. Junio C HamanoFeb 13, 2019
  4. Ævar Arnfjörð BjarmasonFeb 13, 2019
  5. Derrick StoleeFeb 18, 2019
  6. Philip OakleyFeb 15, 2019

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.