Martin von Zweigbergk
@martinvonz on GitHub. Posts as martin.von.zweigbergk@gmail.com, martinvonz@gmail.com.
556
messages
254
patches posted
74%
of 35 series merged
58
threads started
2010
first message, Jan 7, 2010
Dec 10, 2025
since the latest message
Patch series
Of 35 patch series (re-rolls counted once), 26 landed on master and 9 did not.
- not mergedBreakingChanges: say that `git diff X..Y` syntax will be removed in 3.0Oct 15, 2025
- mergedRebase topology testv6, Jun 7, 2013, 2aad7cace2
- mergedreset improvementsv2, Jan 16, 2013, 10746a3616
- mergedtests: move test_cmp_rev to test-lib-functionsDec 21, 2012, 5d77298d08
- mergedoneway_merge(): only lstat() when told to update worktreev2, Dec 20, 2012, 686b2de0ce
- not mergedFix "git reset" on unborn branchNov 29, 2012
- mergedrevision (no-)walking in orderv2, Aug 29, 2012, ca92e59e30
- mergedadd test for 'git rebase --keep-empty'v2, Aug 9, 2012, 2542840344
- mergedSmall log simplificationsv2, Jul 29, 2012, 811929f169
- not mergedcorrectly calculate patches to rebaseJul 18, 2012
- mergedadd test case for rebase of empty commitJun 27, 2012, 2b5ba7b046
- mergedrebase: calculate patches in upstream correctlyJun 26, 2012, 572a7c52bb
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 RFC 00/11] Introduce git-history(1) command for easy history editing
- Re: [PATCH RFC 00/11] Introduce git-history(1) command for easy history editing
- Re: [PATCH v6 00/11] Introduce git-history(1) command for easy history editing
- BreakingChanges: say that `git diff X..Y` syntax will be removed in 3.0
- Re: [PATCH RFC 00/11] Introduce git-history(1) command for easy history editing
- Re: Precious files and the .jj directory
- Histogram/patience diff matching lines with different counts
- Re: Feature request: provide a persistent IDs on a commit
- Re: [PATCH] checkout: special case error messages during noop switching
- Re: Determining if a merge was produced automatically
- Re: Replaying merges
- Re: Current state / standard advice for rebasing merges without information loss/re-entry?
- Re: Current state / standard advice for rebasing merges without information loss/re-entry?
- Re: Current state / standard advice for rebasing merges without information loss/re-entry?
- Re: Current state / standard advice for rebasing merges without information loss/re-entry?
- Re: Current state / standard advice for rebasing merges without information loss/re-entry?
- Re: [RFC] introducing git replay
- Re: Potential bug with octopus merges and symlinks
- Re: Letting tools partially resolve conflicts in a file
- Re: Letting tools partially resolve conflicts in a file
- Letting tools partially resolve conflicts in a file
- Re: Config spec for git
- Generalization of diff and merge
- GC can lose objects pointed to only by notes?
- Re: Can git change?
- Re: Improving merge of tricky conflicts
- Re: Improving merge of tricky conflicts
- Re: [RFC] git checkout $tree -- $path always rewrites files
- Re: [RFC] git checkout $tree -- $path always rewrites files
- Re: [RFC] git checkout $tree -- $path always rewrites files