Philippe Blain
@phil-blain on GitHub. Posts as levraiphilippeblain@gmail.com.
791
messages
381
patches posted
90%
of 63 series merged
94
threads started
2019
first message, Jun 20, 2019
5 days
since the latest message
Patch series
Of 63 patch series (re-rolls counted once), 57 landed on master and 6 did not.
- mergedSome more "Raw output format" doc improvementsMay 15, 2026, 15abb27e3a
- mergedTwo perf test fixesv2, Apr 12, 2025, d17cd9768c
- not mergedrebase -r: a bugfix and two status-related improvementsMar 28, 2025
- mergedDocumentation: fixups following followRemoteHEADFeb 14, 2025, aaf8f79c67
- mergedgit-mergetool: improve error code paths and messagesv2, Nov 22, 2024, fe99a52225
- mergedMakefile: fix dependency for $(UNIT_TEST_DIR)/clar/clar.ov2, Oct 11, 2024, ea3422662d
- mergedt/README: mention test files are make targetsMar 24, 2024, 8d383806fc
- mergedAllow disabling advice shown after merge conflictsv3, Mar 16, 2024, ec0300914b
- mergedci(github): make Windows test artifacts name uniqueMar 10, 2024, e1aaf309db
- not mergedImplement `git log --merge` also for rebase/cherry-pick/revertv6, Feb 28, 2024
- mergedmerge-ort: turn submodule conflict suggestions into an advicev2, Feb 26, 2024, b9e55be740
- mergedcompletion: remove hardcoded config variable namesv3, Feb 10, 2024, 30bd55f901
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 2/2] packfile: fix corruption due to stale delta base cache entries
- Re: [BUG] submodule merge tries to read B's commit from A
- [BUG] "commit graph is likely corrupt" on git rebase
- diff-format.adoc: mode and hash are 0* for unmerged paths from index only
- diff-format.adoc: 'git diff-files' prints two lines for unmerged files
- diff-format.adoc: remove mention of diff-tree specific output
- Some more "Raw output format" doc improvements
- Re: What's cooking in git.git (Apr 2025, #01; Mon, 7)
- Test failure in p5332-multi-pack-reuse.sh
- Re: [PATCH 1/2] p7821: fix test_perf invocation for prereqs
- Re: What's cooking in git.git (Apr 2025, #03; Fri, 11)
- Re: [PATCH v2 0/3] Two perf test fixes
- p7821: fix instructions for testing with threads
- p9210: fix 'scalar clone' when running from a detached HEAD
- p7821: fix test_perf invocation for prereqs
- Two perf test fixes
- Re: What's cooking in git.git (Apr 2025, #03; Fri, 11)
- Re: What's cooking in git.git (Apr 2025, #01; Mon, 7)
- Re: What's cooking in git.git (Apr 2025, #01; Mon, 7)
- p9210: fix 'scalar clone' when running from a detached HEAD
- p7821: fix test_perf invocation for prereqs
- Two perf test fixes
- wt-status: suggest 'git rebase --continue' to conclude 'merge' instruction
- wt-status: also abbreviate 'merge' and 'fixup -C' lines during rebase
- rebase -r: do create merge commit after empty resolution
- rebase -r: a bugfix and two status-related improvements
- Re: [PATCH 2/2] config/remote.txt: improve wording for 'remote.<name>.followRemoteHEAD'
- config/remote.txt: improve wording for 'remote.<name>.followRemoteHEAD'
- config/remote.txt: reunite 'severOption' description paragraphs
- Documentation: fixups following followRemoteHEAD