From: FanJun Kong <bh1scw@gmail.com>
To: git@vger.kernel.org
Cc: FanJun Kong <bh1scw@gmail.com>
Subject: Re: help for git format-patch lost diffstat
Date: Sun, 24 Apr 2022 14:47:30 +0800 [thread overview]
Message-ID: <20220424064730.fdhrgkkkegxbnn3l@kong-HP> (raw)
In-Reply-To: <20220424064114.nwzldz5s2bnkrlu5@kong-HP>
BTW:
I tried 4 different version of git:
git version 2.34.1 fedora
git version 2.32.0 (Apple Git-132)
git version 2.36.0 ubuntu
git version 2.30.2 debian
The result of test is all the same.
On 24 Apr 22 ◦ 14:41, FanJun Kong wrote:
> Hi,
>
> Here are steps of what I am doing:
>
> First, I created two commits to a demo project.
>
> when I use command:
> git format-patch --cover-letter -1
>
> cat 0000-cover-letter.patch
>
> From 2e62ef46d5627319c4cb11be81079e3364fca40c Mon Sep 17 00:00:00 2001
> From: FanJun Kong <bh1scw@gmail.com>
> Date: Sun, 24 Apr 2022 14:31:45 +0800
> Subject: [PATCH 0/1] *** SUBJECT HERE ***
>
> *** BLURB HERE ***
>
> FanJun Kong (1):
> Second commit.
>
> 1.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> --
> 2.32.0 (Apple Git-132)
>
> ok, you can see the cover letter has diffstat, just above "--".
>
> Then I change command to:
>
> git format-patch --cover-letter -2
>
> cat 0000-cover-letter.patch
>
> From 2e62ef46d5627319c4cb11be81079e3364fca40c Mon Sep 17 00:00:00 2001
> From: FanJun Kong <bh1scw@gmail.com>
> Date: Sun, 24 Apr 2022 14:34:48 +0800
> Subject: [PATCH 0/2] *** SUBJECT HERE ***
>
> *** BLURB HERE ***
>
> FanJun Kong (2):
> First commit.
> Second commit.
>
> --
> 2.32.0 (Apple Git-132)
>
> Comparing with last command, I just want to get 2 patches,
> but this time the diffstat is missing.
>
> I am not sure if this is a bug or I miss some options.
>
> I googled this issue, but not got too much.
>
> Thanks for your time.
> Fanjun Kong
next prev parent reply other threads:[~2022-04-24 6:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-24 6:41 help for git format-patch lost diffstat FanJun Kong
2022-04-24 6:47 ` FanJun Kong [this message]
2022-04-25 8:09 ` Eric Sunshine
2022-04-25 9:45 ` FanJun Kong
2022-04-25 17:25 ` Junio C Hamano
2022-04-25 8:14 ` 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=20220424064730.fdhrgkkkegxbnn3l@kong-HP \
--to=bh1scw@gmail.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 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).