From: Konstantin Tokarev <annulen@yandex.ru>
To: Andreas Schwab <schwab@linux-m68k.org>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Bogus error from git log --full-diff
Date: Fri, 19 Jun 2020 19:14:41 +0300 [thread overview]
Message-ID: <585541592583234@mail.yandex.ru> (raw)
In-Reply-To: <87h7v7xf1n.fsf@igel.home>
19.06.2020, 18:59, "Andreas Schwab" <schwab@linux-m68k.org>:
> 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
I've reported this issue in February on this very list and didn't get any reaction from developers.
Seems like it's not considered to be a bug.
--
Regards,
Konstantin
next prev parent reply other threads:[~2020-06-19 16:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-19 15:15 Bogus error from git log --full-diff Andreas Schwab
2020-06-19 16:14 ` Konstantin Tokarev [this message]
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=585541592583234@mail.yandex.ru \
--to=annulen@yandex.ru \
--cc=git@vger.kernel.org \
--cc=schwab@linux-m68k.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).