* How is git diff --relative supposed to work?
@ 2026-01-06 8:15 Johannes Sixt
2026-01-06 10:22 ` Junio C Hamano
0 siblings, 1 reply; 2+ messages in thread
From: Johannes Sixt @ 2026-01-06 8:15 UTC (permalink / raw)
To: Git Mailing List
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?
-- Hannes
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: How is git diff --relative supposed to work?
2026-01-06 8:15 How is git diff --relative supposed to work? Johannes Sixt
@ 2026-01-06 10:22 ` Junio C Hamano
0 siblings, 0 replies; 2+ messages in thread
From: Junio C Hamano @ 2026-01-06 10:22 UTC (permalink / raw)
To: Johannes Sixt; +Cc: Git Mailing List
Johannes Sixt <j6t@kdbg•org> writes:
> 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?
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2026-01-06 10:22 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-01-06 8:15 How is git diff --relative supposed to work? Johannes Sixt
2026-01-06 10:22 ` Junio C Hamano
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox