From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: Re: [BUG?] "format-patch --range-diff=$commit HEAD^ HEAD" fails
Date: Sat, 20 Apr 2024 10:30:31 -0700 [thread overview]
Message-ID: <xmqqcyqk3ps8.fsf@gitster.g> (raw)
In-Reply-To: <xmqqbk65jmqp.fsf@gitster.g> (Junio C. Hamano's message of "Fri, 19 Apr 2024 10:17:18 -0700")
Junio C Hamano <gitster@pobox.com> writes:
> Immediately after "git commit --amend" of a single commit,
> this fails:
>
> $ git format-patch --range-diff=@{1} -v2 HEAD^ HEAD
Please scratch this one. I simply forgot that we have lost
the
git format-patch <his> <mine>
syntax long time ago during Git 1.4.0 timeframe [*]. I somehow was
confused since we still have the corresponding
rebase <since-onto> <mine>
syntax.
[Footnote]
* I suspect this may not have been a conscious design decision but
by accident during the rewrite of the command in C that I started
at 3eefc189 (Tentative built-in format-patch., 2006-04-18) and
whose final shape was documented by 2052d146 (Update
documentation for git-format-patch, 2006-05-31).
prev parent reply other threads:[~2024-04-20 17:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-19 17:17 [BUG?] "format-patch --range-diff=$commit HEAD^ HEAD" fails Junio C Hamano
2024-04-20 17:30 ` Junio C Hamano [this message]
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=xmqqcyqk3ps8.fsf@gitster.g \
--to=gitster@pobox.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.