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

Re: Are --first-parent and --ancestry-path compatible rev-list options?

From
Junio C Hamano <gitster@pobox.com>
Date
Sep 1, 2016, 22:20 UTC
Message-ID
<xmqqd1knuura.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<1BC836ACA8C741AD9732122B3B198752@PhilipOakley>
"Philip Oakley" <philipoakley@iee.org> writes:
Show 6 quoted lines
> The user question was, given a commit 'J', and a future commit 'H'
> (typically a branch tip such as 'master'), find those commits that are
> :
> A) merges
> B) on the first parent DAG chain of the future commit 'H'
> C) children of the given commit 'J'
The answer then is that there is no such single step operation.

In the picture, if D or E were a merge from a side branch that does not have anything to do with 'J', "log --first-parent --merges" will not exclude it (i.e. C won't be fulfilled by --first-parent --merges).

Previous: Philip Oakley
Message 6 of 6 in “Are --first-parent and --ancestry-path compatible rev-list options?”
  1. Philip OakleyAug 26, 2016
  2. Junio C HamanoAug 26, 2016
  3. Philip OakleyAug 27, 2016
  4. Junio C HamanoSep 1, 2016
  5. Philip OakleySep 1, 2016
  6. Junio C HamanoSep 1, 2016

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.