Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com>
Cc: "Marcel Svitalský" <marcel.svitalsky@gmail.com>, git@vger.kernel.org
Subject: Re: Bugreport
Date: Wed, 12 Aug 2026 10:03:21 -0700	[thread overview]
Message-ID: <xmqqmrurxodi.fsf@gitster.g> (raw)
In-Reply-To: <8fe70f89-89a8-426f-bab9-21284722c58d@app.fastmail.com> (Kristoffer Haugsbakk's message of "Wed, 12 Aug 2026 14:54:29 +0200")

"Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com> writes:

>> They are not graphically connected with the actual commits, they just
>> sit there over them. No other graphical
>> tool (Sublime Merge, IntelliJ Idea) displays them.
>
> They are Git notes. They form their own connected graph. That’s why they
> are not connected with the “actual commits” like from some branch.
>
> The `--all` will include all refs, including Git notes like
> `refs/notes/commits`.
>
> This doesn’t look like a bug.

Wow, I 100% agree with your conclusions, but it was unexpected even
to me that "git log --all" crawled anything outside branches,
remote-tracking branches, and tags.  I can sort-of understand why
the "rev-list" command at the plumbing layer may want to include
everything under refs/ hierarchy, but it is unexpected for the
end-user facing "git log".

Not that we want to or we can change it this late in the game,
though.  I wonder if "git log --all -p" also goes through the stash
refs as well as notes.


  parent reply	other threads:[~2026-08-12 17:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-12 12:31 Bugreport Marcel Svitalský
2026-08-12 12:54 ` Bugreport Kristoffer Haugsbakk
2026-08-12 12:59   ` Bugreport Marcel Svitalský
2026-08-12 13:14     ` Bugreport D. Ben Knoble
2026-08-12 13:36       ` Bugreport Marcel Svitalský
2026-08-12 17:04     ` Bugreport Junio C Hamano
2026-08-12 17:26       ` Bugreport Marcel Svitalský
2026-08-12 17:03   ` Junio C Hamano [this message]
     [not found] <AMDPR08MB11409C5DC2EA9B3D8C71FC12BED82A@AMDPR08MB11409.eurprd08.prod.outlook.com>
2026-01-11 17:05 ` Bugreport do Carmo Lucas, Dr. Amilcar (T-PSC)
  -- strict thread matches above, loose matches on Subject: below --
2024-01-19 13:25 Bugreport Frank Schwidom
2024-01-19 23:14 ` Bugreport brian m. carlson
2023-10-24 20:40 bugreport galo joel
2023-11-20  8:36 ` bugreport Thomas Guyot
2020-12-02 10:08 bugreport Ole M
2020-12-02 16:25 ` bugreport Stefan Haller

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=xmqqmrurxodi.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=kristofferhaugsbakk@fastmail.com \
    --cc=marcel.svitalsky@gmail.com \
    /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