Matt Hunter
@trmalfurious on GitHub. Posts as m@lfurio.us.
60
messages
27
patches posted
100%
of 2 series merged
2
threads started
2025
first message, Mar 30, 2025
2 days
since the latest message
Patch series
Of 2 patch series (re-rolls counted once), 2 landed on master and 0 did not.
- mergedIntroduce fetch.followRemoteHEAD config optionv3, Jun 19, 2026, 3e09c9e820
- mergedrevision: fix --left/right-only use with unrelated historiesv2, Mar 30, 2025, e7ef4be7c2
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: Question: behavior when reverting a commit from a shallow clone
- Re: [PATCH v5] fetch.c: defer fetch.followRemoteHEAD validation
- Re: [PATCH v2] fetch.c: defer fetch.followRemoteHEAD validation
- Re: [PATCH] fetch.c: defer fetch.followRemoteHEAD validation
- Re: [PATCH] fetch.c: defer fetch.followRemoteHEAD validation
- Re: What's cooking in git.git (Jul 2026, #12)
- Re: What's cooking in git.git (Jul 2026, #12)
- Re: REBASE_HEAD still exists after success end rebase
- Re: [PATCH v10 0/5] history: add squash subcommand to fold a range
- Re: [PATCH v9 5/5] history: re-edit a squash with every message
- Re: [PATCH v9 3/5] history: add squash subcommand to fold a range
- Re: [PATCH v8 0/5] history: add squash subcommand to fold a range
- Re: [PATCH 4/6] MyFirstContribution: clarify that 'seen' does not mean acceptance
- Re: [PATCH] rebase -i: introduce `pick -x` to add "cherry picked from commit ..."
- Re: Programmatically edit the git rebase sequence?
- Re: Unexpected recursion in 'git rm'
- Re: Unexpected recursion in 'git rm'
- Re: [PATCH] meson: restore hook-list.h to builtin_sources
- Re: [PATCH v5 0/4] history: add squash subcommand to fold a range
- Re: [PATCH v5 0/4] history: add squash subcommand to fold a range
- fetch: fixup a misaligned comment
- fetch: add configuration variable fetch.followRemoteHEAD
- fetch: refactor do_fetch handling of followRemoteHEAD
- doc: explain fetchRemoteHEADWarn advice
- fetch: return 0 on known git_fetch_config
- fetch: rename function report_set_head
- fetch: fixup set_head advice for warn-if-not-branch
- Introduce fetch.followRemoteHEAD config variable
- t5510: cleanup remote in followRemoteHEAD dangling ref test
- Re: [PATCH v2 0/7] Introduce fetch.followRemoteHEAD config variable