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

Re: Finding all commits which modify a file

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 2, 2012, 19:13 UTC
Message-ID
<7vk445vyjn.fsf@alter.siamese.dyndns.org>
In-Reply-To
<5456.38.96.167.131.1328194547.squirrel@mail.lo-cal.org>
"Neal Groothuis" <ngroot@lo-cal.org> writes:
Show 11 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?

Yes. In case my tongue-in-cheek comment was too obscure, I was saying that I do not think the change to TREESAME-ness check you were alluding to would break any use case I would think of off the top of my head.

We of course might discover undesired consequences in unexpected corners after we try your change, but I do not think we can discuss such corner cases further without seeing a patch.

Previous: Neal Groothuis
Message 2 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.