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

Re: Antw: [EXT] Re: Help understanding unexpected diff output

From
Philip Oakley <philipoakley@iee.email>
Date
Oct 23, 2020, 14:24 UTC
Message-ID
<1be0d453-692a-faf7-c72d-225ee7aa12d6@iee.email>
In-Reply-To
<5F0D7252020000A10003A03E@gwsmtp.uni-regensburg.de>

Hi Ulrich, (only just catching up with intriguing queries)

On 14/07/2020 09:52, Ulrich Windl wrote:
> some lines that are not
> changed were reorderd

It may be me, but I think your comment above is at the core of the unexpected diff output.

If text is moved, then normally it will (obviously?) require something within the diff report to say where it was removed from, and then where it was inserted. It seems like your expectation in your use-case was that the moved line changes wouldn't be shown.

I don't believe there is an `--ignore-moved-lines` option, but if there's a good rationale / use-case for it, then maybe it's something to look at coding.

-- Philip

Previous: Junio C Hamano
Message 5 of 5 in “Help understanding unexpected diff output”
  1. Ulrich WindlJul 13, 2020
  2. Junio C HamanoJul 13, 2020
  3. Antw: [EXT] Re: Help understanding unexpected diff outputUlrich Windl, Jul 14, 2020
  4. Junio C HamanoJul 14, 2020
  5. Philip OakleyOct 23, 2020

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.