Miklos Vajna
Posts as vmiklos@frugalware.org, vmiklos@suse.cz.
1,085
messages
457
patches posted
70%
of 137 series merged
140
threads started
2007
first message, Jul 3, 2007
Oct 4, 2013
since the latest message
Patch series
Of 137 patch series (re-rolls counted once), 96 landed on master and 41 did not.
- mergedmerge: allow using --no-ff and --ff-only at the same timev2, Jul 2, 2013, a54841e96b
- mergedcherry-pick: better error message when the parameter is a non-commitv3, Apr 11, 2013, 21246dbb9e
- not mergedcherry-pick -x: improve handling of one-liner commit messagesMar 29, 2013
- mergedcherry-pick: don't forget -s on failurev4, Sep 14, 2012, 5ed75e2a3f
- mergedman: git pull -r is a short for --rebaseAug 16, 2012, d9aa361043
- mergedDocumentation: spelling fixesJun 19, 2012, b4ab1980da
- mergedformat-patch: document the format.to configuration settingJul 12, 2010, 312a30eb5d
- not mergedrebase -i: use 'read -r' to avoid backslash acting as an escape characterJul 6, 2010
- not mergedAdd tests for git format-patch --to and format.to config optionMar 6, 2010
- mergedrequest-pull: avoid mentioning that the start point is a single commitv2, Jan 29, 2010, 10eb00073f
- not mergedIntroduce the GIT_CONFIG_EXTRA environment variableDec 20, 2009
- not mergedgitk Hungarian translation updatesDec 14, 2009
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] Documentation/Makefile: make AsciiDoc dblatex dir configurable
- Re: What's cooking in git.git (Jul 2013, #03; Tue, 9)
- merge: handle --ff/--no-ff/--ff-only as a tri-state option
- merge: handle --ff/--no-ff/--ff-only as a tri-state option
- Re: [PATCH] merge: allow using --no-ff and --ff-only at the same time
- Re: [PATCH] merge: allow using --no-ff and --ff-only at the same time
- merge: allow using --no-ff and --ff-only at the same time
- Re: [PATCH v3] cherry-pick: make sure all input objects are commits
- cherry-pick: make sure all input objects are commits
- Re: [PATCH v2] cherry-pick: make sure all input objects are commits
- cherry-pick: make sure all input objects are commits
- Re: [PATCH] cherry-pick: better error message when the parameter is a non-commit
- cherry-pick: better error message when the parameter is a non-commit
- Re: [PATCH] cherry-pick -x: improve handling of one-liner commit messages
- cherry-pick -x: improve handling of one-liner commit messages
- cherry-pick: don't forget -s on failure
- cherry-pick: don't forget -s on failure
- cherry-pick: don't forget -s on failure
- cherry-pick: don't forget -s on failure
- Re: [PATCH] man: git pull -r is a short for --rebase
- Re: [PATCH] man: git pull -r is a short for --rebase
- Re: [PATCH] man: git pull -r is a short for --rebase
- man: git pull -r is a short for --rebase
- Documentation: spelling fixes
- Re: Deleted file is back - how to investigate?
- Deleted file is back - how to investigate?
- Re: [PATCH 2] Add default merge options for all branches
- Re: gitattributes - clean filter invoked on pull?
- Re: gitattributes - clean filter invoked on pull?
- Re: gitattributes - clean filter invoked on pull?