{"thread":{"id":"63427","subject":"various issues with filtering commits from log","startedAt":"2025-05-09T09:38:24Z","lastAt":"2025-05-09T09:38:24Z","messageCount":1,"participants":["Oswald Buddenhagen"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"517650","messageId":"aB3NDl518qJmQrJQ@ugly","threadId":"63427","inReplyTo":null,"subject":"various issues with filtering commits from log","fromName":"Oswald Buddenhagen","fromEmail":"oswald.buddenhagen@gmx.de","sentAt":"2025-05-09T09:38:22Z","receivedAt":"2025-05-09T09:38:24Z","isPatch":false,"sender":{"key":"oswald.buddenhagen@gmx.de","avatar":"https://avatars.githubusercontent.com/u/812380?v=4"},"body":"moin!\n\ni have to deal with a repo which has relatively little traffic, except \nthat a bot is constantly spamming it, making it basically unfeasible to \nget a quick overview of what happened.\n\nso i thought, \"there certainly is an --exclude-author option, and \nideally, i can persist it in the config as the default\".\nwell, no. what i got is \"--perl-regexp --author='^(?!The Bot)'\". that's \n.. not user friendly.\n\nonce i got there, i noticed that --graph tears apart the history. the \nmanual talks about parent rewriting, but clearly this is not applied to \n_this_ kind of history simplification.\n\nso next i tried to approximate the desired result by logging only the \nmost interesting subdirectory, which the bot luckily doesn't touch. this \nactually looks kinda reasonable, with the catch that a lot of tags & \nbranches are missing from the decorations. this of course makes sense, \nas the relevant commits are not listed. however, it would be rather \ndesirable to have parent rewriting be applied here as well, so \"fake\" \ndecorations would be shown (with an indication where this was done).\n\nthese issues affect \"log --all\" particularly strongly, as it's not \nreally clear what belongs where.\n\nsomewhat unsurprisingly, these issues also affect gitk.\n"}]}