From: Andreas Schwab <schwab@linux-m68k.org>
To: git@vger.kernel.org
Subject: Bogus error from git log --full-diff
Date: Fri, 19 Jun 2020 17:15:32 +0200 [thread overview]
Message-ID: <87h7v7xf1n.fsf@igel.home> (raw)
If you have log.follow=true, then git log --full-diff doesn't work any
more, giving a bogus error:
$ ./git -c log.follow=true log --full-diff .
fatal: --follow requires exactly one pathspec
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next reply other threads:[~2020-06-19 15:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-19 15:15 Andreas Schwab [this message]
2020-06-19 16:14 ` Bogus error from git log --full-diff Konstantin Tokarev
2020-06-19 17:13 ` Junio C Hamano
2020-06-19 17:10 ` 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=87h7v7xf1n.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).