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

Re: How is git diff --relative supposed to work?

From
Junio C Hamano <gitster@pobox.com>
Date
Jan 6, 2026, 10:22 UTC
Message-ID
<xmqqfr8jjb1g.fsf@gitster.g>
In-Reply-To
<f1cd3ca7-9b31-45b0-b990-05f4d1f6b4f2@kdbg.org>
Johannes Sixt <j6t@kdbg.org> writes:
Show 8 quoted lines
> Try this in your favorite repository:
>
> $ echo foo >> Makefile
> $ git -P diff --name-only --relative=Ma
> kefile
>
> This doesn't look right. Shouldn't the path specified with --relative be
> interpreted as a directory instead of an arbitrary textual prefix?

Sounds like an utter nonsense to me, too. If we assume Ma were a directory, would the result be "../Makefile" relative to the Ma directory?

Previous: Johannes Sixt
Message 2 of 2 in “How is git diff --relative supposed to work?”
  1. Johannes SixtJan 6, 2026
  2. Junio C HamanoJan 6, 2026

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.