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

Re: [PATCH] rev-list: fix --reverse interaction with --parents

From
Johannes Sixt <johannes.sixt@telecom.at>
Date
Aug 29, 2008, 19:53 UTC
Message-ID
<200808292153.59376.johannes.sixt@telecom.at>
In-Reply-To
<1220037518-11219-1-git-send-email-trast@student.ethz.ch>
On Freitag, 29. August 2008, Thomas Rast wrote:
Show 10 quoted lines
> Johannes Sixt wrote:
> > This command does not give the expected result: It reports *two* initial
> > commits and one merge; in particular, commit X is reported as initial
> > commit.
> >
> > $ git rev-list --parents --reverse --full-history master -- P2
>
> The good news is: the patch really does fix your issue.  It also fixes
> the test case (which uses the history from the diagram above).  And it
> passes the test suite.

Thanks for picking up the topic and helping out. It does indeed work with my example.

I let others comment whether this patch is good. I've no clue how the revision walker machinery works.

-- Hannes
Previous: Thomas RastNext: Junio C Hamano
Message 3 of 4 in “rev-list --reverse --full-history --parents with path limiter disconnects history”
  1. Johannes SixtAug 21, 2008
  2. rev-list: fix --reverse interaction with --parentsThomas Rast, Aug 29, 2008
  3. Johannes SixtAug 29, 2008
  4. Junio C HamanoAug 31, 2008

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.