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

Re: Finding all commits which modify a file

From
NGNeal Groothuis <ngroot@lo-cal.org>
Date
Feb 2, 2012, 14:55 UTC
Message-ID
<5456.38.96.167.131.1328194547.squirrel@mail.lo-cal.org>
Show 7 quoted lines
> "Neal Groothuis" <ngroot@lo-cal.org> writes:
>
>> Is there a situation where checking for TREESAMEness before
>> simplification
>> is desirable and checking after would not be?
>
> When you do not want to see a side branch that does not contribute to

the end result at all, obviously ;-). Outside that situation, before or after should not make a difference, I would think.

In that case, you wouldn't be using the --full-history flag at all, yeah?

Right now, we can see where the file gets changed (A1), we just can't see where it gets changed back (B2). In fact, if I run git-log --full-history --simplify-merges foo.txt, it looks like A1 was the last thing to make changes to foo.txt, which seems misleading to me---history has been simplified to the point of not being true.

Next: Junio C Hamano
Message 1 of 2 in “Re: Finding all commits which modify a file”
  1. Neal GroothuisFeb 2, 2012
  2. Junio C HamanoFeb 2, 2012

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.