Git development
 help / color / mirror / Atom feed
From: "Marcel Svitalský" <marcel.svitalsky@gmail.com>
To: "D. Ben Knoble" <ben.knoble@gmail.com>
Cc: Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>,
	git@vger.kernel.org
Subject: Re: Bugreport
Date: Wed, 12 Aug 2026 15:36:06 +0200	[thread overview]
Message-ID: <e832d095-2a6f-4e98-b20a-f21175bfc817@gmail.com> (raw)
In-Reply-To: <CALnO6CD-nWAJhaMqAPCL9NOHUtqbna6Z=RHZVrE_WfOeC6bdsw@mail.gmail.com>

On 12/08/2026 15:14, D. Ben Knoble wrote:
> [please don't top-post]
>
>
>> On 12/08/2026 14:54, Kristoffer Haugsbakk wrote:
>>> I have only skimmed this.
>>>
>>> On Wed, Aug 12, 2026, at 14:31, Marcel Svitalský wrote:
>>>> What did you do before the bug happened? (Steps to reproduce your issue)
>>>> I called `git lg` command to display git graph log in my terminal. The
>>>> command is defined in my
>>>> general gitconfig file as follows:
>>>>
>>>> # double liner with hash, time, branches and tags on first line and the
>>>> message on second
>>>> lg = "!f() { num=15; if [ \"$1\" != \"\" ] && ( echo \"$1\" | grep -q
>>>> \"^[0-9]\\\\+\\$\" ) ; then num=\"$1\" ; shift ; fi ; [ $num -eq 0 ] &&
>>>> num=999999999 ; git \"$@\" log -n \"$num\" --graph --abbrev-commit
>>>> --decorate --format=format:'%C(bold blue)%h%C(reset) - %C(bold
>>>> cyan)%aD%C(reset) %C(bold green)(%ar)%C(reset)%C(bold
>>>> yellow)%d%C(reset)%n'' %C(white)%s%C(reset)' --all; }; f"
>>> Note the `--all`.
>>>
>>>> What did you expect to happen? (Expected behavior)
>>>> I expected to see git graph log with the project commits.
>>>>
>>>> What happened instead? (Actual behavior)
>>>> On top of the project commits were added these four pseudo-commits made
>>>> by some Git component(s).
>>>>
>>>> * f7b611ce - Wed, 12 Aug 2026 09:26:03 +0200 (5 hours ago)
>>>> |  Notes added by 'git notes append' - rewrite-analytics
>>>> * 1a7605bb - Wed, 12 Aug 2026 09:26:03 +0200 (5 hours ago)
>>>> |  Notes added by 'git notes append' - rewrite-analytics
>>>> * c2a05d79 - Wed, 12 Aug 2026 09:25:03 +0200 (5 hours ago)
>>>> |  Notes added by 'git notes append' - rewrite-analytics
>>>>     \
>>>>      * 01c630e0 - Wed, 12 Aug 2026 09:13:00 +0200 (5 hours ago)
>>>>         chatter: initialize notes ref - chatter
>>>>
>>>> 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.
>>>
>>>> [snip]
> On Wed, Aug 12, 2026 at 9:03 AM Marcel Svitalský
> <marcel.svitalsky@gmail.com> wrote:
>> I see, thank you. Is this a new feature? I've been using this command
>> for years
>> and today is the first time I am seeing this.
> Notes are not new. Perhaps a tool you use started creating them?

I suspect lazygit. Or Idea, I don't know and won't investigate any further.

>> Also, is there another
>> flag instead of
>> `--all` that would just include the actual commits only?
> You could limit the refs to be listed, like maybe "--branches --tags
> --remotes", or "--exclude='refs/notes/*' --all" ? (I'm omitting
> treatment of refs/stash, too, for now.)

Works fine, thank you very much (and yes, I now realize I could and 
should have
looked at the man page to begin with).

I suppose this can be closed now (I do not know the procedures here). 
Thanks again!

MS

  reply	other threads:[~2026-08-12 13:36 UTC|newest]

Thread overview: 14+ 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       ` Marcel Svitalský [this message]
2026-08-12 17:04     ` Bugreport Junio C Hamano
2026-08-12 17:03   ` Bugreport Junio C Hamano
     [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=e832d095-2a6f-4e98-b20a-f21175bfc817@gmail.com \
    --to=marcel.svitalsky@gmail.com \
    --cc=ben.knoble@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=kristofferhaugsbakk@fastmail.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