From: Johannes Sixt <j6t@kdbg•org>
To: Git Mailing List <git@vger•kernel.org>
Subject: How is git diff --relative supposed to work?
Date: Tue, 6 Jan 2026 09:15:03 +0100 [thread overview]
Message-ID: <f1cd3ca7-9b31-45b0-b990-05f4d1f6b4f2@kdbg.org> (raw)
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
next reply other threads:[~2026-01-06 8:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-06 8:15 Johannes Sixt [this message]
2026-01-06 10:22 ` How is git diff --relative supposed to work? Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f1cd3ca7-9b31-45b0-b990-05f4d1f6b4f2@kdbg.org \
--to=j6t@kdbg$(echo .)org \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox