Bernhard R. Link
Posts as brlink@debian.org.
20
messages
9
patches posted
0%
of 2 series merged
3
threads started
2009
first message, Nov 30, 2009
Jan 13, 2014
since the latest message
Patch series
Of 2 patch series (re-rolls counted once), 0 landed on master and 2 did not.
- not mergedLet format-patch and rebase ignore trivial merges.v2, Dec 18, 2009
- not mergedadd new command git equal-tree-markerNov 30, 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
- [RFC v2] blame: new option --prefer-first to better handle merged cherry-picks
- Re: [PATCH/RFC 4/4] Add interactive mode to git-shell for user-friendliness
- Re: [PATCH 4/4] Makefile: Don't pass $(ALL_CFLAGS) to the linker
- Re: [PATCH] Handle double slashes in make_relative_path()
- Let format-patch and rebase ignore trivial merges.
- Re: [PATCH] Let format-patch and rebase ignore trivial merges.
- Re: [PATCH] Let format-patch and rebase ignore trivial merges.
- Re: [PATCH] Let format-patch and rebase ignore trivial merges.
- Let format-patch and rebase ignore trivial merges.
- Re: equal-tree-merges as way to make rebases fast-forward-able
- Re: equal-tree-merges as way to make rebases fast-forward-able
- Re: equal-tree-merges as way to make rebases fast-forward-able
- add support for creating equal tree markers to rebase -i
- add support for creating equal tree markers after rebase
- make rebase -m equal tree marker aware
- support equal tree merges in interactive rebase
- format-patch defaults to --first-equal-tree-only
- add option to only visit the first parent of a equal tree merge
- add new command git equal-tree-marker
- equal-tree-merges as way to make rebases fast-forward-able