brian m. carlson
@bk2204 on GitHub. Posts as sandals@crustytoothpaste.ath.cx, sandals@crustytoothpaste.net.
5,594
messages
2,874
patches posted
80%
of 176 series merged
274
threads started
2007
first message, Dec 3, 2007
11 hours
since the latest message
Patch series
Of 178 patch series (re-rolls counted once), 140 landed on master and 36 did not; 2 posted in the last 90 days are still in review.
- in reviewGit 3.0: restrict hex object IDs to lowercase onlyv2, Sep 7, 2026
- in reviewMakefile: read configuration earlierJul 29, 2026
- mergedRust hash cleanupsJul 19, 2026, 251e7af992
- mergedrev-parse: exit 0 on --helpv3, Jul 8, 2026, 06f9b9501a
- mergedcommit: name UTF-8 function appropriatelyv2, Apr 27, 2026, 1ddc0481cf
- mergedEnable Rust by defaultv2, Apr 9, 2026, 6077dc8a42
- mergeddocs: correct information about reftableApr 2, 2026, e2f25d202e
- not mergedfsck: do not loop infinitely when processing packsFeb 22, 2026
- mergedSHA-1/SHA-256 interoperability, part 2v3, Feb 7, 2026, e25c7c9393
- mergedgitfaq: document using stash import/export to sync working treeJan 9, 2026, 02fc44a989
- mergedcheckout: quote invalid treeish in error messageDec 24, 2025, 93f894c001
- not mergedFix doc default hash algorithm in WITH_BREAKING_CHANGES modeDec 2, 2025
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: [RFC PATCH 1/1] SubmittingPatches: allow responsible AI assistance
- Re: [RFC PATCH 0/4] sign a SHA-256 digest of the tree in commits and tags
- Re: [RFC PATCH 0/4] sign a SHA-256 digest of the tree in commits and tags
- Re: [RFC PATCH 0/4] sign a SHA-256 digest of the tree in commits and tags
- Re: [RFC PATCH 0/4] sign a SHA-256 digest of the tree in commits and tags
- Re: [PATCH] doc: add more examples of overriding LESS in core.pager
- Re: [RFC PATCH 0/4] sign a SHA-256 digest of the tree in commits and tags
- Re: [PATCH 1/4] libgitcore: add `sha1dc` as an optional feature
- Re: a "limbo" object-format state for empty repositories?
- Re: a "limbo" object-format state for empty repositories?
- Re: Confusion with git config list --show-origin
- Re: [BUG] branch copy/rename update refs without running the reference-transaction hook
- Re: Windows: ~1 GB RAM per git process, many concurrent (2.56.0.windows.1)
- Re: [RFC PATCH 0/4] sign a SHA-256 digest of the tree in commits and tags
- Re: [RFC] git stash: add porcelain for sharing stashes through remotes
- Re: [RFC] Optional per-repository consent before running local hooks
- Re: [PATCH] name-rev: update hash descriptions
- Re: [DOC] name-rev: --annotate-stdin docs still describe SHA-1
- Re: pager: consider revisiting automatic LESS=FRX with custom core.pager
- Re: [PATCH/RFC] commit: warn when a new commit is dated before its parent
- Re: [PATCH v3] Move rust gitcore crate to a different subdirectory
- Re: What will come after Git 2.56?
- Re: [PATCH 3/3] imap-send: only check the CN if no SAN DNS names are present
- object-name: use hexval
- t5324: adjust tests for corrupt commit-graph
- hex: allow only lowercase object IDs in breaking changes mode
- Git 3.0: restrict hex object IDs to lowercase only
- hex: label usages of hex parsing for object IDs
- hex: add functionality for lowercase-only hex
- hex: allow specifying hex type with hex2chr