From: Wang Yugui <wangyugui@e16-tech.com>
To: git@vger.kernel.org
Subject: git format-patch lost the last part when branch merge
Date: Mon, 22 Feb 2021 21:16:21 +0800 [thread overview]
Message-ID: <20210222211621.0C5D.409509F4@e16-tech.com> (raw)
Hi,
git format-patch lost the last part when branch merge
Here is an example.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
Merge tag 'for-5.12/block-2021-02-17' of git://git.kernel.dk/linux-block
1, from the web interface,
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/fs/btrfs?id=582cd91f69de8e44857cb610ebca661dac8656b7
the last part 'diff --git a/fs/btrfs/zoned.c b/fs/btrfs/zoned.c' can be confirmed.
2, but from ' commit | 582cd91f69de8e44857cb610ebca661dac8656b7 (patch)' of this web page,
the last part 'diff --git a/fs/btrfs/zoned.c b/fs/btrfs/zoned.c' is not in the patch file.
3, git format-patch 4f016a316f22.. fs/btrfs/ will not output 'diff --git a/fs/btrfs/zoned.c b/fs/btrfs/zoned.c' too.
Best Regards
[System Info]
git version:
git version 2.30.1 and 2.27.0
cpu: x86_64
no commit associated with this build
sizeof-long: 8
sizeof-size_t: 8
shell-path: /bin/sh
uname: Linux 5.10.17-3.el7.x86_64 #1 SMP Mon Feb 22 10:43:13 CST 2021 x86_64
compiler info: gnuc: 4.8
libc info: glibc: 2.17
$SHELL (typically, interactive shell): /bin/bash
[Enabled Hooks]
None
Best Regards
王玉贵
2021/02/22
--------------------------------------
北京京垓科技有限公司
王玉贵 wangyugui@e16-tech.com
电话:+86-136-71123776
next reply other threads:[~2021-02-22 13:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-22 13:16 Wang Yugui [this message]
2021-02-22 22:57 ` git format-patch lost the last part when branch merge Jeff King
2021-02-22 23:08 ` [PATCH] docs/format-patch: mention handling of merges Jeff King
2021-02-22 23:31 ` Junio C Hamano
2021-02-22 23:40 ` Jeff King
2021-02-23 1:24 ` Junio C Hamano
2021-02-23 1:48 ` Jeff King
2021-02-22 23:25 ` git format-patch lost the last part when branch merge Junio C Hamano
2021-02-24 4:24 ` Elijah Newren
2021-02-24 4:50 ` Jeff King
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=20210222211621.0C5D.409509F4@e16-tech.com \
--to=wangyugui@e16-tech.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.