From: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
To: git@vger.kernel.org
Subject: bug in `git log --cherry-mark`
Date: Tue, 14 Jul 2026 09:56:20 +0200 [thread overview]
Message-ID: <alXmoXCs1VtE-KVr@monoceros> (raw)
[-- Attachment #1: Type: text/plain, Size: 2410 bytes --]
Hello,
in a linux tree I have a bunch of commits that I sent out for
application to the mainline. A part of that looks as follows:
$ git version # that's 2.55.0 + Phillip Wood's series addressing my previous bug report
git version 2.55.0.11.g153666a7d9bb
$ git log --pretty=oneline --abbrev-commit --decorate --boundary --graph --cherry-mark --right-only next/master...a54cadc575df
* a54cadc575df merge mod_devicetable.h cleanups
|\
| * fc69191474ff virtio-pci: Drop inclusion of <linux/mod_devicetable.h>
| * 80964227feed greybus: Drop #include of <linux/mod_devicetable.h>
| * ede7ce64f20e Documentation: Update after split of <linux/mod_devicetable.h>
| * c8efa35aeff7 HID: wacom: #include <linux/device-id/hid.h> instead of <linux/mod_devicetable.h>
| * baead64db0b9 checkpatch: Adapt comment to mod_devicetable.h split
| * ca270a534d0f net: phy: Drop #inclusion of <linux/mod_devicetable.h> from <linux/mdio.h>
* | 9874577217c5 WIP: Don't build XFS on m68k due to https://gcc.gnu.org/bugzilla/show_bug.cgi?id=122438
* | 554e345d3223 s390: export memory encryption helper functions
* | 41d6dc9f88ec Add defconfigs for x86 and arm64 to yield stable builds
* | 9a6220166a5e drm/vmwgfx: Don't use UTS_RELEASE directly
o | 49362394dad7 (tag: next-20260713, next/master, next/HEAD) Add linux-next specific files for 20260713
/
o 8cdeaa50eae8 (tag: v7.2-rc2) Linux 7.2-rc2
So this suggests that all the commits are not yet in next. But if I look
at the right branch only, one actually is:
$ git log --pretty=oneline --abbrev-commit --decorate --boundary --graph --cherry-mark --right-only next/master...a54cadc575df^2
* fc69191474ff virtio-pci: Drop inclusion of <linux/mod_devicetable.h>
* 80964227feed greybus: Drop #include of <linux/mod_devicetable.h>
* ede7ce64f20e Documentation: Update after split of <linux/mod_devicetable.h>
* c8efa35aeff7 HID: wacom: #include <linux/device-id/hid.h> instead of <linux/mod_devicetable.h>
* baead64db0b9 checkpatch: Adapt comment to mod_devicetable.h split
= ca270a534d0f net: phy: Drop #inclusion of <linux/mod_devicetable.h> from <linux/mdio.h>
o 8cdeaa50eae8 (tag: v7.2-rc2) Linux 7.2-rc2
I would have expected that ca270a534d0f is marked with = already in the
upper dump. Is my expectation wrong here, or is that a bug?
If you want to look at it, I can provide the relevant commits in a
bundle via private mail.
Best regards
Uwe
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
reply other threads:[~2026-07-14 7:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=alXmoXCs1VtE-KVr@monoceros \
--to=u.kleine-koenig@baylibre.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.