{"thread":{"id":"66163","subject":"Bugreport","startedAt":"2026-08-12T12:31:48Z","lastAt":"2026-08-13T05:00:22Z","messageCount":9,"participants":["Marcel Svitalský","Kristoffer Haugsbakk","D. Ben Knoble","Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"550396","messageId":"a7899757-9c3d-4735-b7ab-469808707e61@gmail.com","threadId":"66163","inReplyTo":null,"subject":"Bugreport","fromName":"Marcel Svitalský","fromEmail":"marcel.svitalsky@gmail.com","sentAt":"2026-08-12T12:31:45Z","receivedAt":"2026-08-12T12:31:48Z","isPatch":false,"body":"What did you do before the bug happened? (Steps to reproduce your issue)\nI called `git lg` command to display git graph log in my terminal. The \ncommand is defined in my\ngeneral gitconfig file as follows:\n\n# double liner with hash, time, branches and tags on first line and the \nmessage on second\nlg = \"!f() { num=15; if [ \\\"$1\\\" != \\\"\\\" ] && ( echo \\\"$1\\\" | grep -q \n\\\"^[0-9]\\\\\\\\+\\\\$\\\" ) ; then num=\\\"$1\\\" ; shift ; fi ; [ $num -eq 0 ] && \nnum=999999999 ; git \\\"$@\\\" log -n \\\"$num\\\" --graph --abbrev-commit \n--decorate --format=format:'%C(bold blue)%h%C(reset) - %C(bold \ncyan)%aD%C(reset) %C(bold green)(%ar)%C(reset)%C(bold \nyellow)%d%C(reset)%n'' %C(white)%s%C(reset)' --all; }; f\"\n\nWhat did you expect to happen? (Expected behavior)\nI expected to see git graph log with the project commits.\n\nWhat happened instead? (Actual behavior)\nOn top of the project commits were added these four pseudo-commits made \nby some Git component(s).\n\n* f7b611ce - Wed, 12 Aug 2026 09:26:03 +0200 (5 hours ago)\n|  Notes added by 'git notes append' - rewrite-analytics\n* 1a7605bb - Wed, 12 Aug 2026 09:26:03 +0200 (5 hours ago)\n|  Notes added by 'git notes append' - rewrite-analytics\n* c2a05d79 - Wed, 12 Aug 2026 09:25:03 +0200 (5 hours ago)\n|  Notes added by 'git notes append' - rewrite-analytics\n  \\\n   * 01c630e0 - Wed, 12 Aug 2026 09:13:00 +0200 (5 hours ago)\n      chatter: initialize notes ref - chatter\n\nThey are not graphically connected with the actual commits, they just \nsit there over them. No other graphical\ntool (Sublime Merge, IntelliJ Idea) displays them.\nOriginally, when I opened the project, only the first (chronologically) \ncommit (by chatter) appeared,\nand those by rewrite-analytics seem to be added with actual commits in \nbranches, each for one branch.\nSometimes after more commits or merges they disappear and after removing \n(`git reset --hard`) those new\ncommits/merges they re-appear (I played with it a little).\nThey are not always on top, sometimes when a new commit in a branch is \nmade it gets on top and these\npseudo-commits sit beside (to the right) of the graph log, still \nunconnected.\n\nWhat's different between what you expected and what actually happened?\nThose pseudo-commits.\n\nAnything else you want to add: The terminal is tmux running on \nmate-terminal.\n\nPlease review the rest of the bug report below.\nYou can delete any lines you don't wish to share.\n\n\n[System Info]\ngit version:\ngit version 2.55.0.559.g11c6700f10\ncpu: x86_64\nbuilt from commit: 11c6700f10234578d10523faf35656ca491425c9\nsizeof-long: 8\nsizeof-size_t: 8\nshell-path: /bin/sh\nrust: enabled\nfeature: fsmonitor--daemon\ngettext: enabled\nlibcurl: 8.21.0\nOpenSSL: OpenSSL 3.6.3 9 Jun 2026\nzlib: 1.3.2\nSHA-1: SHA1_DC\nSHA-256: SHA256_BLK\ndefault-ref-format: files\ndefault-hash: sha1\nuname: Linux 7.1.6-1-MANJARO #1 SMP PREEMPT_DYNAMIC Mon, 03 Aug 2026 \n10:34:01 +0000 x86_64\ncompiler info: gnuc: 16.1\nlibc info: glibc: 2.44\n$SHELL (typically, interactive shell): /bin/bash\n\n\n[Enabled Hooks]\n\n"},{"id":"550397","messageId":"8fe70f89-89a8-426f-bab9-21284722c58d@app.fastmail.com","threadId":"66163","inReplyTo":"a7899757-9c3d-4735-b7ab-469808707e61@gmail.com","subject":"Re: Bugreport","fromName":"Kristoffer Haugsbakk","fromEmail":"kristofferhaugsbakk@fastmail.com","sentAt":"2026-08-12T12:54:29Z","receivedAt":"2026-08-12T12:55:10Z","isPatch":false,"body":"I have only skimmed this.\n\nOn Wed, Aug 12, 2026, at 14:31, Marcel Svitalský wrote:\n> What did you do before the bug happened? (Steps to reproduce your issue)\n> I called `git lg` command to display git graph log in my terminal. The\n> command is defined in my\n> general gitconfig file as follows:\n>\n> # double liner with hash, time, branches and tags on first line and the\n> message on second\n> lg = \"!f() { num=15; if [ \\\"$1\\\" != \\\"\\\" ] && ( echo \\\"$1\\\" | grep -q\n> \\\"^[0-9]\\\\\\\\+\\\\$\\\" ) ; then num=\\\"$1\\\" ; shift ; fi ; [ $num -eq 0 ] &&\n> num=999999999 ; git \\\"$@\\\" log -n \\\"$num\\\" --graph --abbrev-commit\n> --decorate --format=format:'%C(bold blue)%h%C(reset) - %C(bold\n> cyan)%aD%C(reset) %C(bold green)(%ar)%C(reset)%C(bold\n> yellow)%d%C(reset)%n'' %C(white)%s%C(reset)' --all; }; f\"\n\nNote the `--all`.\n\n> What did you expect to happen? (Expected behavior)\n> I expected to see git graph log with the project commits.\n>\n> What happened instead? (Actual behavior)\n> On top of the project commits were added these four pseudo-commits made\n> by some Git component(s).\n>\n> * f7b611ce - Wed, 12 Aug 2026 09:26:03 +0200 (5 hours ago)\n> |  Notes added by 'git notes append' - rewrite-analytics\n> * 1a7605bb - Wed, 12 Aug 2026 09:26:03 +0200 (5 hours ago)\n> |  Notes added by 'git notes append' - rewrite-analytics\n> * c2a05d79 - Wed, 12 Aug 2026 09:25:03 +0200 (5 hours ago)\n> |  Notes added by 'git notes append' - rewrite-analytics\n>   \\\n>    * 01c630e0 - Wed, 12 Aug 2026 09:13:00 +0200 (5 hours ago)\n>       chatter: initialize notes ref - chatter\n>\n> They are not graphically connected with the actual commits, they just\n> sit there over them. No other graphical\n> tool (Sublime Merge, IntelliJ Idea) displays them.\n\nThey are Git notes. They form their own connected graph. That’s why they\nare not connected with the “actual commits” like from some branch.\n\nThe `--all` will include all refs, including Git notes like\n`refs/notes/commits`.\n\nThis doesn’t look like a bug.\n\n>[snip]\n"},{"id":"550398","messageId":"f4e39b04-b6dd-4b83-9103-8a1c98019dce@gmail.com","threadId":"66163","inReplyTo":"8fe70f89-89a8-426f-bab9-21284722c58d@app.fastmail.com","subject":"Re: Bugreport","fromName":"Marcel Svitalský","fromEmail":"marcel.svitalsky@gmail.com","sentAt":"2026-08-12T12:59:52Z","receivedAt":"2026-08-12T12:59:56Z","isPatch":false,"body":"I see, thank you. Is this a new feature? I've been using this command \nfor years\nand today is the first time I am seeing this. Also, is there another \nflag instead of\n`--all` that would just include the actual commits only?\n\nThank you, best regards\nMarcel Svitalský\n\nOn 12/08/2026 14:54, Kristoffer Haugsbakk wrote:\n> I have only skimmed this.\n>\n> On Wed, Aug 12, 2026, at 14:31, Marcel Svitalský wrote:\n>> What did you do before the bug happened? (Steps to reproduce your issue)\n>> I called `git lg` command to display git graph log in my terminal. The\n>> command is defined in my\n>> general gitconfig file as follows:\n>>\n>> # double liner with hash, time, branches and tags on first line and the\n>> message on second\n>> lg = \"!f() { num=15; if [ \\\"$1\\\" != \\\"\\\" ] && ( echo \\\"$1\\\" | grep -q\n>> \\\"^[0-9]\\\\\\\\+\\\\$\\\" ) ; then num=\\\"$1\\\" ; shift ; fi ; [ $num -eq 0 ] &&\n>> num=999999999 ; git \\\"$@\\\" log -n \\\"$num\\\" --graph --abbrev-commit\n>> --decorate --format=format:'%C(bold blue)%h%C(reset) - %C(bold\n>> cyan)%aD%C(reset) %C(bold green)(%ar)%C(reset)%C(bold\n>> yellow)%d%C(reset)%n'' %C(white)%s%C(reset)' --all; }; f\"\n> Note the `--all`.\n>\n>> What did you expect to happen? (Expected behavior)\n>> I expected to see git graph log with the project commits.\n>>\n>> What happened instead? (Actual behavior)\n>> On top of the project commits were added these four pseudo-commits made\n>> by some Git component(s).\n>>\n>> * f7b611ce - Wed, 12 Aug 2026 09:26:03 +0200 (5 hours ago)\n>> |  Notes added by 'git notes append' - rewrite-analytics\n>> * 1a7605bb - Wed, 12 Aug 2026 09:26:03 +0200 (5 hours ago)\n>> |  Notes added by 'git notes append' - rewrite-analytics\n>> * c2a05d79 - Wed, 12 Aug 2026 09:25:03 +0200 (5 hours ago)\n>> |  Notes added by 'git notes append' - rewrite-analytics\n>>    \\\n>>     * 01c630e0 - Wed, 12 Aug 2026 09:13:00 +0200 (5 hours ago)\n>>        chatter: initialize notes ref - chatter\n>>\n>> They are not graphically connected with the actual commits, they just\n>> sit there over them. No other graphical\n>> tool (Sublime Merge, IntelliJ Idea) displays them.\n> They are Git notes. They form their own connected graph. That’s why they\n> are not connected with the “actual commits” like from some branch.\n>\n> The `--all` will include all refs, including Git notes like\n> `refs/notes/commits`.\n>\n> This doesn’t look like a bug.\n>\n>> [snip]\n\n"},{"id":"550399","messageId":"CALnO6CD-nWAJhaMqAPCL9NOHUtqbna6Z=RHZVrE_WfOeC6bdsw@mail.gmail.com","threadId":"66163","inReplyTo":"f4e39b04-b6dd-4b83-9103-8a1c98019dce@gmail.com","subject":"Re: Bugreport","fromName":"D. Ben Knoble","fromEmail":"ben.knoble@gmail.com","sentAt":"2026-08-12T13:14:07Z","receivedAt":"2026-08-12T13:14:20Z","isPatch":false,"body":"[please don't top-post]\n\n\n> On 12/08/2026 14:54, Kristoffer Haugsbakk wrote:\n> > I have only skimmed this.\n> >\n> > On Wed, Aug 12, 2026, at 14:31, Marcel Svitalský wrote:\n> >> What did you do before the bug happened? (Steps to reproduce your issue)\n> >> I called `git lg` command to display git graph log in my terminal. The\n> >> command is defined in my\n> >> general gitconfig file as follows:\n> >>\n> >> # double liner with hash, time, branches and tags on first line and the\n> >> message on second\n> >> lg = \"!f() { num=15; if [ \\\"$1\\\" != \\\"\\\" ] && ( echo \\\"$1\\\" | grep -q\n> >> \\\"^[0-9]\\\\\\\\+\\\\$\\\" ) ; then num=\\\"$1\\\" ; shift ; fi ; [ $num -eq 0 ] &&\n> >> num=999999999 ; git \\\"$@\\\" log -n \\\"$num\\\" --graph --abbrev-commit\n> >> --decorate --format=format:'%C(bold blue)%h%C(reset) - %C(bold\n> >> cyan)%aD%C(reset) %C(bold green)(%ar)%C(reset)%C(bold\n> >> yellow)%d%C(reset)%n'' %C(white)%s%C(reset)' --all; }; f\"\n> > Note the `--all`.\n> >\n> >> What did you expect to happen? (Expected behavior)\n> >> I expected to see git graph log with the project commits.\n> >>\n> >> What happened instead? (Actual behavior)\n> >> On top of the project commits were added these four pseudo-commits made\n> >> by some Git component(s).\n> >>\n> >> * f7b611ce - Wed, 12 Aug 2026 09:26:03 +0200 (5 hours ago)\n> >> |  Notes added by 'git notes append' - rewrite-analytics\n> >> * 1a7605bb - Wed, 12 Aug 2026 09:26:03 +0200 (5 hours ago)\n> >> |  Notes added by 'git notes append' - rewrite-analytics\n> >> * c2a05d79 - Wed, 12 Aug 2026 09:25:03 +0200 (5 hours ago)\n> >> |  Notes added by 'git notes append' - rewrite-analytics\n> >>    \\\n> >>     * 01c630e0 - Wed, 12 Aug 2026 09:13:00 +0200 (5 hours ago)\n> >>        chatter: initialize notes ref - chatter\n> >>\n> >> They are not graphically connected with the actual commits, they just\n> >> sit there over them. No other graphical\n> >> tool (Sublime Merge, IntelliJ Idea) displays them.\n> > They are Git notes. They form their own connected graph. That’s why they\n> > are not connected with the “actual commits” like from some branch.\n> >\n> > The `--all` will include all refs, including Git notes like\n> > `refs/notes/commits`.\n> >\n> > This doesn’t look like a bug.\n> >\n> >> [snip]\n\nOn Wed, Aug 12, 2026 at 9:03 AM Marcel Svitalský\n<marcel.svitalsky@gmail.com> wrote:\n>\n> I see, thank you. Is this a new feature? I've been using this command\n> for years\n> and today is the first time I am seeing this.\n\nNotes are not new. Perhaps a tool you use started creating them?\n\n> Also, is there another\n> flag instead of\n> `--all` that would just include the actual commits only?\n\nYou could limit the refs to be listed, like maybe \"--branches --tags\n--remotes\", or \"--exclude='refs/notes/*' --all\" ? (I'm omitting\ntreatment of refs/stash, too, for now.)\n\n\n-- \nD. Ben Knoble\n"},{"id":"550408","messageId":"e832d095-2a6f-4e98-b20a-f21175bfc817@gmail.com","threadId":"66163","inReplyTo":"CALnO6CD-nWAJhaMqAPCL9NOHUtqbna6Z=RHZVrE_WfOeC6bdsw@mail.gmail.com","subject":"Re: Bugreport","fromName":"Marcel Svitalský","fromEmail":"marcel.svitalsky@gmail.com","sentAt":"2026-08-12T13:36:06Z","receivedAt":"2026-08-12T13:36:09Z","isPatch":false,"body":"On 12/08/2026 15:14, D. Ben Knoble wrote:\n> [please don't top-post]\n>\n>\n>> On 12/08/2026 14:54, Kristoffer Haugsbakk wrote:\n>>> I have only skimmed this.\n>>>\n>>> On Wed, Aug 12, 2026, at 14:31, Marcel Svitalský wrote:\n>>>> What did you do before the bug happened? (Steps to reproduce your issue)\n>>>> I called `git lg` command to display git graph log in my terminal. The\n>>>> command is defined in my\n>>>> general gitconfig file as follows:\n>>>>\n>>>> # double liner with hash, time, branches and tags on first line and the\n>>>> message on second\n>>>> lg = \"!f() { num=15; if [ \\\"$1\\\" != \\\"\\\" ] && ( echo \\\"$1\\\" | grep -q\n>>>> \\\"^[0-9]\\\\\\\\+\\\\$\\\" ) ; then num=\\\"$1\\\" ; shift ; fi ; [ $num -eq 0 ] &&\n>>>> num=999999999 ; git \\\"$@\\\" log -n \\\"$num\\\" --graph --abbrev-commit\n>>>> --decorate --format=format:'%C(bold blue)%h%C(reset) - %C(bold\n>>>> cyan)%aD%C(reset) %C(bold green)(%ar)%C(reset)%C(bold\n>>>> yellow)%d%C(reset)%n'' %C(white)%s%C(reset)' --all; }; f\"\n>>> Note the `--all`.\n>>>\n>>>> What did you expect to happen? (Expected behavior)\n>>>> I expected to see git graph log with the project commits.\n>>>>\n>>>> What happened instead? (Actual behavior)\n>>>> On top of the project commits were added these four pseudo-commits made\n>>>> by some Git component(s).\n>>>>\n>>>> * f7b611ce - Wed, 12 Aug 2026 09:26:03 +0200 (5 hours ago)\n>>>> |  Notes added by 'git notes append' - rewrite-analytics\n>>>> * 1a7605bb - Wed, 12 Aug 2026 09:26:03 +0200 (5 hours ago)\n>>>> |  Notes added by 'git notes append' - rewrite-analytics\n>>>> * c2a05d79 - Wed, 12 Aug 2026 09:25:03 +0200 (5 hours ago)\n>>>> |  Notes added by 'git notes append' - rewrite-analytics\n>>>>     \\\n>>>>      * 01c630e0 - Wed, 12 Aug 2026 09:13:00 +0200 (5 hours ago)\n>>>>         chatter: initialize notes ref - chatter\n>>>>\n>>>> They are not graphically connected with the actual commits, they just\n>>>> sit there over them. No other graphical\n>>>> tool (Sublime Merge, IntelliJ Idea) displays them.\n>>> They are Git notes. They form their own connected graph. That’s why they\n>>> are not connected with the “actual commits” like from some branch.\n>>>\n>>> The `--all` will include all refs, including Git notes like\n>>> `refs/notes/commits`.\n>>>\n>>> This doesn’t look like a bug.\n>>>\n>>>> [snip]\n> On Wed, Aug 12, 2026 at 9:03 AM Marcel Svitalský\n> <marcel.svitalsky@gmail.com> wrote:\n>> I see, thank you. Is this a new feature? I've been using this command\n>> for years\n>> and today is the first time I am seeing this.\n> Notes are not new. Perhaps a tool you use started creating them?\n\nI suspect lazygit. Or Idea, I don't know and won't investigate any further.\n\n>> Also, is there another\n>> flag instead of\n>> `--all` that would just include the actual commits only?\n> You could limit the refs to be listed, like maybe \"--branches --tags\n> --remotes\", or \"--exclude='refs/notes/*' --all\" ? (I'm omitting\n> treatment of refs/stash, too, for now.)\n\nWorks fine, thank you very much (and yes, I now realize I could and \nshould have\nlooked at the man page to begin with).\n\nI suppose this can be closed now (I do not know the procedures here). \nThanks again!\n\nMS\n"},{"id":"550427","messageId":"xmqqmrurxodi.fsf@gitster.g","threadId":"66163","inReplyTo":"8fe70f89-89a8-426f-bab9-21284722c58d@app.fastmail.com","subject":"Re: Bugreport","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2026-08-12T17:03:21Z","receivedAt":"2026-08-12T17:03:23Z","isPatch":false,"body":"\"Kristoffer Haugsbakk\" <kristofferhaugsbakk@fastmail.com> writes:\n\n>> They are not graphically connected with the actual commits, they just\n>> sit there over them. No other graphical\n>> tool (Sublime Merge, IntelliJ Idea) displays them.\n>\n> They are Git notes. They form their own connected graph. That’s why they\n> are not connected with the “actual commits” like from some branch.\n>\n> The `--all` will include all refs, including Git notes like\n> `refs/notes/commits`.\n>\n> This doesn’t look like a bug.\n\nWow, I 100% agree with your conclusions, but it was unexpected even\nto me that \"git log --all\" crawled anything outside branches,\nremote-tracking branches, and tags.  I can sort-of understand why\nthe \"rev-list\" command at the plumbing layer may want to include\neverything under refs/ hierarchy, but it is unexpected for the\nend-user facing \"git log\".\n\nNot that we want to or we can change it this late in the game,\nthough.  I wonder if \"git log --all -p\" also goes through the stash\nrefs as well as notes.\n\n"},{"id":"550428","messageId":"xmqqik5fxobr.fsf@gitster.g","threadId":"66163","inReplyTo":"f4e39b04-b6dd-4b83-9103-8a1c98019dce@gmail.com","subject":"Re: Bugreport","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2026-08-12T17:04:24Z","receivedAt":"2026-08-12T17:04:27Z","isPatch":false,"body":"Marcel Svitalský <marcel.svitalsky@gmail.com> writes:\n\n> I see, thank you. Is this a new feature? I've been using this command \n> for years\n> and today is the first time I am seeing this. Also, is there another \n> flag instead of\n> `--all` that would just include the actual commits only?\n\n--branches\n--tags\n--remotes\n\n"},{"id":"550433","messageId":"ab3a0ca8-82e9-4387-b363-2f851760a946@gmail.com","threadId":"66163","inReplyTo":"xmqqik5fxobr.fsf@gitster.g","subject":"Re: Bugreport","fromName":"Marcel Svitalský","fromEmail":"marcel.svitalsky@gmail.com","sentAt":"2026-08-12T17:26:20Z","receivedAt":"2026-08-12T17:26:24Z","isPatch":false,"body":"On 12/08/2026 19:04, Junio C Hamano wrote:\n> Marcel Svitalský <marcel.svitalsky@gmail.com> writes:\n>\n>> I see, thank you. Is this a new feature? I've been using this command\n>> for years\n>> and today is the first time I am seeing this. Also, is there another\n>> flag instead of\n>> `--all` that would just include the actual commits only?\n> --branches\n> --tags\n> --remotes\n>\n\nThank you, I actually want stashes included in the log so I chose the\n`--exclude='refs/notes/*' --all` solution suggested by D. Ben Knoble.\n\nMS\n"},{"id":"550468","messageId":"25c18566-134b-49af-86e8-494634fe51f5@app.fastmail.com","threadId":"66163","inReplyTo":"xmqqmrurxodi.fsf@gitster.g","subject":"Re: Bugreport","fromName":"Kristoffer Haugsbakk","fromEmail":"kristofferhaugsbakk@fastmail.com","sentAt":"2026-08-13T04:59:57Z","receivedAt":"2026-08-13T05:00:22Z","isPatch":false,"body":"On Wed, Aug 12, 2026, at 19:03, Junio C Hamano wrote:\n> \"Kristoffer Haugsbakk\" <kristofferhaugsbakk@fastmail.com> writes:\n>>[snip]\n>>\n>> They are Git notes. They form their own connected graph. That’s why they\n>> are not connected with the “actual commits” like from some branch.\n>>\n>> The `--all` will include all refs, including Git notes like\n>> `refs/notes/commits`.\n>>\n>> This doesn’t look like a bug.\n>\n> Wow, I 100% agree with your conclusions, but it was unexpected even\n> to me that \"git log --all\" crawled anything outside branches,\n> remote-tracking branches, and tags.  I can sort-of understand why\n> the \"rev-list\" command at the plumbing layer may want to include\n> everything under refs/ hierarchy, but it is unexpected for the\n> end-user facing \"git log\".\n\nMaybe `--all` was added before Git notes and that was the intent? Well,\nthey would known that it would include whatever custom refs that people\nwanted. But then maybe they thought of it as:\n\n• branches, remote-tracking branches, tags (from git(1))\n• (git-stash(1) is an old command; I think it might have been an\n  oversight to include it with `--all`? (see end of this message))\n• whatever custom refs the repo uses; these you should know (?) and\n  shouldn’t get surprised by\n\nThe custom refs would have been added by third-party programs, but\nsomeone would have thought that it was worth going through the effort of\npushing out these refs to other people. Although, people could still be\nsurprised by mere bookkeeping data showing up with `--all`.[1]\n\n***\n\nNote for others: One doesn’t end up with Git notes added by git(1)[1]\n*by others* that easily. ;) Branches and tags can be pushed out easily,\nbut you need an explicit refspec to push Git notes. And I don’t think\ngit-notes(1) mentions this. I would venture to bet that most people who\nhave learned to push out Git notes have learned it from StackOverflow or\nsome other not-Git project site.\n\nAnd after someone has gone through the trouble of pushing them, other\npeople also need to fetch them with an explicit refspec.\n\n† 1: By other programs is a different matter. Git notes are a great way\n     to attach metadata to commits, so many third-party tools use\n     that. And it might not matter to the end-user whether data about\n     which commit messages have typos in them is stored in Git notes or\n     in some Sqlite database, but `--all` will reveal that\n     implementation detail if Notes are used.\n\n>\n> Not that we want to or we can change it this late in the game,\n> though.  I wonder if \"git log --all -p\" also goes through the stash\n> refs as well as notes.\n\nIt does show the commits from `refs/stash`.\n"}]}