Miklos Vajna
@vmiklos on GitHub. Posts as vmiklos@collabora.com.
40
messages
29
patches posted
100%
of 1 series merged
2
threads started
2026
first message, May 5, 2026
4 days
since the latest message
Patch series
Of 2 patch series (re-rolls counted once), 1 landed on master and 0 did not; 1 posted in the last 90 days is still in review.
- in reviewlog: speed up --follow following renames for non-linear historyv5, Nov 16, 2026
- mergedlog: let --follow follow renames in merge commitsv4, Jun 22, 2026, 304812ed33
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 v2] log: make --follow following renames for non-linear history optional
- log: make --follow following renames for non-linear history optional
- log: make --follow following renames for non-linear history optional
- Re: [PATCH v5 0/5] log: speed up --follow following renames for non-linear history
- log: speed up --follow following renames for non-linear history
- log: simplify --follow following renames for non-linear history
- log: fix -m --follow losing the history of later parents
- log: extract showing the remerge/combined diff of a merge commit
- t4219: test more --follow cases across merges
- log: speed up --follow following renames for non-linear history
- Re: [PATCH v4 6/6] log: fix --follow following an edit on a side the merge did not take
- Re: [PATCH v4 5/6] log: speed up --follow following renames for non-linear history
- Re: [PATCH v4 0/6] log: speed up --follow following renames for non-linear history
- log: fix --follow following an edit on a side the merge did not take
- log: speed up --follow following renames for non-linear history
- log: simplify --follow following renames for non-linear history
- log: fix -m --follow losing the history of later parents
- log: extract showing the remerge/combined diff of a merge commit
- t4219: test more --follow cases across merges
- log: speed up --follow following renames for non-linear history
- log: speed up --follow following renames for non-linear history
- log: simplify --follow following renames for non-linear history
- log: extract showing the remerge/combined diff of a merge commit
- t4219: test more --follow cases across merges
- log: speed up --follow following renames for non-linear history
- log: speed up --follow following renames for non-linear history
- log: speed up --follow following renames for non-linear history
- Re: Performance regression in `git log --follow`
- Re: [PATCH v4] log: improve --follow following renames for non-linear history
- log: improve --follow following renames for non-linear history