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

Re: format-patch on permission change gives empty patch

From
Junio C Hamano <gitster@pobox.com>
Date
Oct 7, 2010, 20:29 UTC
Message-ID
<7vmxqpwxue.fsf@alter.siamese.dyndns.org>
In-Reply-To
<alpine.LFD.2.00.1010071503210.3107@xanadu.home>
Nicolas Pitre <nico@fluxnic.net> writes:
Show 9 quoted lines
> On Wed, 6 Oct 2010, Junio C Hamano wrote:
>
>> I have a mixed feeling about where to go next.
>> 
>>  (1) Treat "rebase" as a way to reproduce a reasonable history; the
>>      current behaviour to drop empty commits is consistent with this view,
>>      as a history with an empty commit is _not_ entirely reasonable.
>
> But a file mode change isn't exactly an empty commit, no?
The second message from DaveM:
    Message-ID: <20101006.174008.70175671.davem@davemloft.net>
    Ok it turns out that the commit in question was a NOP since the file
    permissions didn't change.
Previous: Nicolas Pitre
Message 9 of 9 in “format-patch on permission change gives empty patch”
  1. David MillerOct 7, 2010
  2. David MillerOct 7, 2010
  3. Junio C HamanoOct 7, 2010
  4. Junio C HamanoOct 7, 2010
  5. Sverre RabbelierOct 7, 2010
  6. Jakub NarebskiOct 7, 2010
  7. Sverre RabbelierOct 7, 2010
  8. Nicolas PitreOct 7, 2010
  9. Junio C HamanoOct 7, 2010

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.