Tao Klerks
@TaoK on GitHub. Posts as tao@klerks.biz.
273
messages
83
patches posted
61%
of 18 series merged
49
threads started
2020
first message, Apr 20, 2020
Apr 29, 2025
since the latest message
Patch series
Of 18 patch series (re-rolls counted once), 11 landed on master and 7 did not.
- not mergedreplace-refs: fix support of qualified replace ref pathsApr 26, 2025
- not mergedRFC: apply: support case-only renames in case-insensitive filesystemsv3, May 28, 2023
- not mergedrev-parse: respect push.autosetupremote when evaluating @{push}v2, May 28, 2023
- not mergedcherry-pick: refuse cherry-pick sequence if index is dirtyv2, May 28, 2023
- not mergedRFC: switch: allow same-commit switch during merge if conflicts resolvedMay 2, 2023
- mergedmergetool: new config guiDefault supports auto-toggling gui by DISPLAYv4, Mar 18, 2023, 42943b950e
- not mergedpull: conflict hint pull.rebase suggestion should offer "merges" vs "true"Feb 5, 2023
- mergedrev-parse: documentation adjustment - mention remote tracking with @{u}v2, Jun 23, 2022, 8cdab69d96
- merged[RFC] git-p4: improve encoding handling to support inconsistent encodingsv4, Apr 30, 2022, f7b5ff607f
- not mergedt3200: fix antipatterns in existing branch testsv3, Apr 30, 2022
- mergedadding new branch.autosetupmerge option "simple"v5, Apr 29, 2022, bdaf1dfae7
- mergedgit-p4: preserve utf8 BOM when importing from p4 to gitApr 4, 2022, fbe5f6b804
A series is merged when one of its patches matches a commit on master by the same author, by subject. Versions are linked when they share a patch subject. Patches reworded before landing, or applied under someone else's name, count as not merged.
Recent emails
- Re: [PATCH] replace-refs: fix support of qualified replace ref paths
- replace-refs: fix support of qualified replace ref paths
- Python-based fetch optimizer script for "blame" in Partial Clones (was: Re: Sensible way to see what objects are being fetched just-in-time in a partial clone?)
- Re: Sensible way to see what objects are being fetched just-in-time in a partial clone?
- Can git log be made to "follow" in the same way as git blame? Why / in what way is "--follow" broken or limited?
- Sensible way to see what objects are being fetched just-in-time in a partial clone?
- Is --minimal ever not the right thing?
- Re: Is "bare"ness in the context of multiple worktrees weird? Bitmap error in git gc.
- Re: Is "bare"ness in the context of multiple worktrees weird? Bitmap error in git gc.
- Re: [PATCH v2] cherry-pick: refuse cherry-pick sequence if index is dirty
- Re: Plumbing for mapping from a remote tracking ref to the remote ref?
- Re: Is "bare"ness in the context of multiple worktrees weird? Bitmap error in git gc.
- Re: Is "bare"ness in the context of multiple worktrees weird? Bitmap error in git gc.
- Re: Is "bare"ness in the context of multiple worktrees weird? Bitmap error in git gc.
- Re: Is "bare"ness in the context of multiple worktrees weird? Bitmap error in git gc.
- Re: Is "bare"ness in the context of multiple worktrees weird? Bitmap error in git gc.
- Is "bare"ness in the context of multiple worktrees weird? Bitmap error in git gc.
- Re: Plumbing for mapping from a remote tracking ref to the remote ref?
- Re: "git fetch --refetch" and multiple (separate/orphan) branches
- Re: Determining whether you have a commit locally, in a partial clone?
- Re: Determining whether you have a commit locally, in a partial clone?
- Re: Determining whether you have a commit locally, in a partial clone?
- Re: Determining whether you have a commit locally, in a partial clone?
- Determining whether you have a commit locally, in a partial clone?
- Re: [BUGREPORT] Why is git-push fetching content?
- "git fetch --refetch" and multiple (separate/orphan) branches
- Re: When someone creates a new worktree by copying an existing one
- Re: When someone creates a new worktree by copying an existing one
- apply: support case-only renames in case-insensitive filesystems
- reset: new failing test for reset of case-insensitive duplicate in index