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

Re: git-rev-list bug?

From
CMCatalin Marinas <catalin.marinas@arm.com>
Date
Mar 10, 2006, 11:01 UTC
Message-ID
<tnx64mmpnq4.fsf@arm.com>
In-Reply-To
<7vslpqy4u7.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano <junkio@cox.net> wrote:
Show 13 quoted lines
> Junio C Hamano <junkio@cox.net> writes:
>
>> It however has a side effect -- uninteresting commits were never
>> parsed here, but now they get parsed.  I am not sure if there
>> are correctness implications...
>
> Actually there is.  If a merge with an uninteresting side branch
> was the only thing that brought changes to paths we are
> interested in, we do not want TREE_SAME logic to remove other
> parents (i.e. the branches we are interested in) from the merge
> commit.  
>
> So we would need a combination of both, something like this?

I can confirm that it "stg patches" works fine with this patch for git-rev-list.

Thanks.
-- 
Catalin
Previous: Junio C HamanoNext: Linus Torvalds
Message 7 of 9 in “git-rev-list bug?”
  1. Catalin MarinasMar 8, 2006
  2. Junio C HamanoMar 8, 2006
  3. Junio C HamanoMar 10, 2006
  4. Junio C HamanoMar 10, 2006
  5. Junio C HamanoMar 10, 2006
  6. Junio C HamanoMar 10, 2006
  7. Catalin MarinasMar 10, 2006
  8. Linus TorvaldsMar 10, 2006
  9. Junio C HamanoMar 10, 2006

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.