# Tao Klerks GitHub: https://github.com/TaoK Addresses: tao@klerks.biz Messages: 273. Patches: 83. Threads started: 49. First message: 2020-04-20T21:18:55Z. Latest: 2025-04-29T19:36:05Z. ## Messages per year | Year | Messages | Patches | |---|---|---| | 2020 | 4 | 0 | | 2021 | 24 | 6 | | 2022 | 186 | 67 | | 2023 | 53 | 9 | | 2024 | 4 | 0 | | 2025 | 2 | 1 | ## Patch series 11 merged, 7 not merged, 0 in review (posted in the last 90 days); acceptance rate 61%. Re-rolls count once; merged means a patch matches a commit on master by the same author. - 2025-04-26 not merged: [replace-refs: fix support of qualified replace ref paths](https://gitlist.dev/t/63354) - 2023-05-28 not merged (v3): [RFC: apply: support case-only renames in case-insensitive filesystems](https://gitlist.dev/t/57986) - 2023-05-28 not merged (v2): [rev-parse: respect push.autosetupremote when evaluating @{push}](https://gitlist.dev/t/58128) - 2023-05-28 not merged (v2): [cherry-pick: refuse cherry-pick sequence if index is dirty](https://gitlist.dev/t/59782) - 2023-05-02 not merged: [RFC: switch: allow same-commit switch during merge if conflicts resolved](https://gitlist.dev/t/59681) - 2023-03-18 merged (v4): [mergetool: new config guiDefault supports auto-toggling gui by DISPLAY](https://gitlist.dev/t/58611) commit 42943b950e12 - 2023-02-05 not merged: [pull: conflict hint pull.rebase suggestion should offer "merges" vs "true"](https://gitlist.dev/t/59200) - 2022-06-23 merged (v2): [rev-parse: documentation adjustment - mention remote tracking with @{u}](https://gitlist.dev/t/58036) commit 8cdab69d967e - 2022-04-30 merged (v4): [[RFC] git-p4: improve encoding handling to support inconsistent encodings](https://gitlist.dev/t/57709) commit f7b5ff607fa1 - 2022-04-30 not merged (v3): [t3200: fix antipatterns in existing branch tests](https://gitlist.dev/t/57589) - 2022-04-29 merged (v5): [adding new branch.autosetupmerge option "simple"](https://gitlist.dev/t/57470) commit bdaf1dfae71f - 2022-04-04 merged: [git-p4: preserve utf8 BOM when importing from p4 to git](https://gitlist.dev/t/57655) commit fbe5f6b80437 - 2022-04-04 merged: [git-p4: support explicit sync of arbitrary existing git-p4 refs](https://gitlist.dev/t/57654) commit 17f273ffbad8 - 2022-04-01 merged (v7): [tracking branches: add advice to ambiguous refspec error](https://gitlist.dev/t/57591) commit e4921d877ab3 - 2022-03-31 merged (v6): [Support untracked cache with '--untracked-files=all' if configured](https://gitlist.dev/t/55990) commit e6a653554bb4 - 2022-03-02 merged (v3): [Reduce explicit sleep calls in t7063 untracked cache tests](https://gitlist.dev/t/57482) commit 090a3085bc9f - 2022-02-27 merged (v3): [Empty untracked cache performance issue](https://gitlist.dev/t/56002) commit a67d178be4e6 - 2021-06-02 merged: [Remove warning that repack only works on non-promisor packfiles](https://gitlist.dev/t/55830) commit ace6d8e3d66b ## Recent emails - 2025-04-29 [Re: [PATCH] replace-refs: fix support of qualified replace ref paths](https://gitlist.dev/e/CAPMMpohgEXVPHKCQtvc-zLC35qtY%2BqJ9WgQO_quOgUG01eyTOw%40mail.gmail.com) - 2025-04-26 [[PATCH] replace-refs: fix support of qualified replace ref paths](https://gitlist.dev/e/pull.1903.git.1745651452869.gitgitgadget%40gmail.com) - 2024-08-26 [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?)](https://gitlist.dev/e/CAPMMpojae7t1Z0PQPf%3Dd2WzzbaMwkhvo34b_sxdtUQxvDu4fJw%40mail.gmail.com) - 2024-08-26 [Re: Sensible way to see what objects are being fetched just-in-time in a partial clone?](https://gitlist.dev/e/CAPMMpoiPeSyLHUd072Q9AozdaCAjpOL03jY-0Y33B2iEQ5EdTQ%40mail.gmail.com) - 2024-08-26 [Can git log be made to "follow" in the same way as git blame? Why / in what way is "--follow" broken or limited?](https://gitlist.dev/e/CAPMMpogApZ6VN9sYxgmtHCickkstM6HZq1teeAa%2Ba2t1_BY0sQ%40mail.gmail.com) - 2024-08-26 [Sensible way to see what objects are being fetched just-in-time in a partial clone?](https://gitlist.dev/e/CAPMMpog7%3DZnhJhrgZFwzRZibLtK1-LyOhsrp5c4O85ocRFDZxw%40mail.gmail.com) - 2023-12-19 [Is --minimal ever not the right thing?](https://gitlist.dev/e/CAPMMpohbQK%2B3o46iiY%2B0o%3DvS%2BUC_HBB%3DCxsNT_hAb5dDz%2B514Q%40mail.gmail.com) - 2023-09-07 [Re: Is "bare"ness in the context of multiple worktrees weird? Bitmap error in git gc.](https://gitlist.dev/e/CAPMMpojTLswqubRk0Ly3RQqkrnpx_9Hiu_TRK1%3DASPbPNz4ApQ%40mail.gmail.com) - 2023-09-06 [Re: Is "bare"ness in the context of multiple worktrees weird? Bitmap error in git gc.](https://gitlist.dev/e/CAPMMpohgkH3h1zC_Q7O-07gYw8_7mdSsyX7vu1K1u5%2BCxKUaUQ%40mail.gmail.com) - 2023-09-06 [Re: [PATCH v2] cherry-pick: refuse cherry-pick sequence if index is dirty](https://gitlist.dev/e/CAPMMpoj8udDuDferkaRfoKDV6EHMVO6fH3_GE9SUN51VKbwvJA%40mail.gmail.com) - 2023-09-06 [Re: Plumbing for mapping from a remote tracking ref to the remote ref?](https://gitlist.dev/e/CAPMMpoh7%3DriapMO-91e81MrK-uR%2Bsm7ttgCu8433dNNQU0ZsQw%40mail.gmail.com) - 2023-09-05 [Re: Is "bare"ness in the context of multiple worktrees weird? Bitmap error in git gc.](https://gitlist.dev/e/CAPMMpogm2tr0dy1nsV9NtF4O8-JS%3D_L3J0%2ByKRc7KbyAJ-PNbQ%40mail.gmail.com) - 2023-09-05 [Re: Is "bare"ness in the context of multiple worktrees weird? Bitmap error in git gc.](https://gitlist.dev/e/CAPMMpog3o%3DDtOrC9L6ED42XkegdObkh3rGm617q4u2oofBC1TA%40mail.gmail.com) - 2023-09-05 [Re: Is "bare"ness in the context of multiple worktrees weird? Bitmap error in git gc.](https://gitlist.dev/e/CAPMMpohc-pOD33NE_wSwYnMYKQYEtAQ64B2qwKZmUM38Euk9mw%40mail.gmail.com) - 2023-09-04 [Re: Is "bare"ness in the context of multiple worktrees weird? Bitmap error in git gc.](https://gitlist.dev/e/CAPMMpohpKJdopSpZu%2BehE0MZrH8cksgtY1NEHFyZz2jj%2BLOKhA%40mail.gmail.com) - 2023-09-04 [Re: Is "bare"ness in the context of multiple worktrees weird? Bitmap error in git gc.](https://gitlist.dev/e/CAPMMpoj7s%3DewXJfJyxvrcHjpmOOWEWBvZ94OOuVmYs2UQ482HA%40mail.gmail.com) - 2023-09-04 [Is "bare"ness in the context of multiple worktrees weird? Bitmap error in git gc.](https://gitlist.dev/e/CAPMMpoixKnr4BkKd8jeU%2B79Edhqtu4R7m8%3DBX4ZSYKdBHDzK%3Dw%40mail.gmail.com) - 2023-09-03 [Re: Plumbing for mapping from a remote tracking ref to the remote ref?](https://gitlist.dev/e/CAPMMpojUrfSmpgWVh3TTn_uamPCcyHRQf2R3APSpEjsqujNXvA%40mail.gmail.com) - 2023-08-10 [Re: "git fetch --refetch" and multiple (separate/orphan) branches](https://gitlist.dev/e/CAPMMpoh9xP8PomAUTHGZfYAMAgHb_BF74EVgmo1C-DQh22-cUA%40mail.gmail.com) - 2023-06-21 [Re: Determining whether you have a commit locally, in a partial clone?](https://gitlist.dev/e/CAPMMpoha6rBA-T-7cn3DQT_nbNfknigLTky55x0TEmt4Ay2GRA%40mail.gmail.com) - 2023-06-20 [Re: Determining whether you have a commit locally, in a partial clone?](https://gitlist.dev/e/CAPMMpoj%2B5XT9LwL%3D%3Dih-cmdYyz6RN6Ysr%3Dg661keTOTH-QrK-g%40mail.gmail.com) - 2023-06-20 [Re: Determining whether you have a commit locally, in a partial clone?](https://gitlist.dev/e/CAPMMpojUpJD21x2i_hshTB96TBFVd-_WRV54KHT2-4R8DUh8%3DQ%40mail.gmail.com) - 2023-06-20 [Re: Determining whether you have a commit locally, in a partial clone?](https://gitlist.dev/e/CAPMMpog8Hv_KcjNxbh_wzjwrFYt7TuTvrVy1XEtJMm6RWSKzRg%40mail.gmail.com) - 2023-06-20 [Determining whether you have a commit locally, in a partial clone?](https://gitlist.dev/e/CAPMMpohiTzANyhzL-mS-gg2kzbOEOiDktNbdwEXBKy9uL0-JgA%40mail.gmail.com) - 2023-06-20 [Re: [BUGREPORT] Why is git-push fetching content?](https://gitlist.dev/e/CAPMMpoiC8oca0AVNy1f%2Bzy26L_b-ADyNopY4zO3r%2Bv6v-KEH%3DA%40mail.gmail.com) - 2023-06-02 ["git fetch --refetch" and multiple (separate/orphan) branches](https://gitlist.dev/e/CAPMMpoiJ4cNcAR9gO5d-749N3YW-88p1gMnX8ySGgz84Mr9coA%40mail.gmail.com) - 2023-06-02 [Re: When someone creates a new worktree by copying an existing one](https://gitlist.dev/e/CAPMMpoikxfpcoN1T7A6FD76MSAvBqjJNsc55-mJc2ubM7gUAYw%40mail.gmail.com) - 2023-06-01 [Re: When someone creates a new worktree by copying an existing one](https://gitlist.dev/e/CAPMMpoi9vy1xyvpAHE6qCwgazLSg%3Du4rR9eX098Gf9VL60XSOg%40mail.gmail.com) - 2023-05-28 [[PATCH v3 3/3] apply: support case-only renames in case-insensitive filesystems](https://gitlist.dev/e/52359738532ab89c4612e4b83f08ab50fa169dd4.1685267999.git.gitgitgadget%40gmail.com) - 2023-05-28 [[PATCH v3 2/3] reset: new failing test for reset of case-insensitive duplicate in index](https://gitlist.dev/e/ab1cdd95e03c8f0a9896898b34ceab7b67bee3b5.1685267999.git.gitgitgadget%40gmail.com)