Junio C Hamano
@gitster on GitHub. Posts as gitster@pobox.com, junio@hera.kernel.org, junio@pobox.com, junio@twinsun.com, junkio@cox.net, junkio@twinsun.com.
89,417
messages
5,275
patches posted
73%
of 1,999 series merged
4,408
threads started
2005
first message, Apr 13, 2005
2 hours
since the latest message
Patch series
Of 2,003 patch series (re-rolls counted once), 1,466 landed on master and 533 did not; 4 posted in the last 90 days are still in review.
- in reviewRe* [PATCH v10 4/4] hook: introduce the receive-report hookv10, Sep 14, 2026
- mergedcocci: remove risky "if (!E) free(E)" conversionSep 11, 2026, d870565117
- in reviewMore sensible checkout/switch/restore code refactoringv2, Aug 30, 2026
- mergedyou_still_use_that(): reword the instructionsv3, Aug 27, 2026, 8ace32221c
- in reviewdie_for_incompatible_opts(): unbounded number of optionsv2, Aug 27, 2026
- mergedrerere: technical documentation typofixAug 24, 2026, d2af22cc21
- mergedcompletion of 'git [-C <dir>] checkout'v3, Aug 13, 2026, 735514635b
- mergedcompletion of 'git [-C <dir>] diff'v6, Aug 12, 2026, 4b1b7a4e95
- mergedgit add --resolvedv3, Jul 31, 2026, e28c701fe4
- in reviewgit stash drop stash@{2.days.ago}Jul 30, 2026
- mergedremote: plug memory leaksv2, Jul 25, 2026, dcef3bf041
- mergedrevision: honor --exclude-first-parent-only with SEEN first parentJul 22, 2026, 47382f7398
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 v8 4/5] remote: add "git remote add --limited-fetch"
- Re: [PATCH v8 2/5] fetch: extract collect_upstream_from_remote() helper
- Re: [PATCH v2 1/6] doc: add new gitmergeconflicts man page
- What's cooking in git.git (Oct 2026, #04)
- Re: [PATCH v3 2/2] merge: remember conflict labels
- Re: [PATCH 0/4] faster SHA-1 collision detection
- Re: [PATCH v2 1/6] doc: add new gitmergeconflicts man page
- Re: [PATCH v3 1/1] repo: add filtering options to "repo structure"
- Re: [PATCH] wincred: fix line split of secret blob content
- Re: [RFC PATCH 1/1] SubmittingPatches: allow responsible AI assistance
- Re: [PATCH v3 0/2] checkout -m: recreate conflict labels
- Re: [PATCH 8/8] ci: drop redundant linux-reftable job
- Re: [PATCH v2 2/2] blame: ignore revs in HEAD:.git-blame-ignore-revs
- Re: [PATCH v2] stash: expose untracked modes in create
- Re: [PATCH v3] status: suggest `git merge --continue`, not `git commit`
- Re: [PATCH v2 0/6] [doc] Add new page on merge conflicts
- Re: [PATCH v2 6/6] doc: git-pull: link to new merge conflicts guide
- Re: [PATCH v2 5/6] doc: git-cherry-pick: link to new merge conflicts guide
- Re: [PATCH v2 4/6] doc: git-revert: link to new merge conflicts guide
- Re: [PATCH v2 3/6] doc: git-rebase: link to new merge conflicts guide
- Re: [PATCH v2 2/6] doc: git-merge: link to new merge conflicts guide
- Re: [PATCH v2 1/6] doc: add new gitmergeconflicts man page
- Re: [PATCH v2 0/6] [doc] Add new page on merge conflicts
- Re: [PATCH v3 0/5] repack: don't lose objects to a ".keep" that appears mid-run
- Re: [PATCH 1/2] read-cache: do not trust a size change when conversion is active
- Re: [PATCH v2 1/2] blame: harden ignore-revs parser and tag peeling
- Re: [PATCH 0/4] faster SHA-1 collision detection
- Re: [PATCH 1/2] worktree repair: refactor and reduce .git file reads
- Re: [PATCH] t7004: check a missing key without deleting gpghome
- Re: [PATCH v3 0/5] repack: don't lose objects to a ".keep" that appears mid-run