* various issues with filtering commits from log
@ 2025-05-09 9:38 Oswald Buddenhagen
0 siblings, 0 replies; only message in thread
From: Oswald Buddenhagen @ 2025-05-09 9:38 UTC (permalink / raw)
To: git
moin!
i have to deal with a repo which has relatively little traffic, except
that a bot is constantly spamming it, making it basically unfeasible to
get a quick overview of what happened.
so i thought, "there certainly is an --exclude-author option, and
ideally, i can persist it in the config as the default".
well, no. what i got is "--perl-regexp --author='^(?!The Bot)'". that's
.. not user friendly.
once i got there, i noticed that --graph tears apart the history. the
manual talks about parent rewriting, but clearly this is not applied to
_this_ kind of history simplification.
so next i tried to approximate the desired result by logging only the
most interesting subdirectory, which the bot luckily doesn't touch. this
actually looks kinda reasonable, with the catch that a lot of tags &
branches are missing from the decorations. this of course makes sense,
as the relevant commits are not listed. however, it would be rather
desirable to have parent rewriting be applied here as well, so "fake"
decorations would be shown (with an indication where this was done).
these issues affect "log --all" particularly strongly, as it's not
really clear what belongs where.
somewhat unsurprisingly, these issues also affect gitk.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2025-05-09 9:38 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-05-09 9:38 various issues with filtering commits from log Oswald Buddenhagen
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox