Andrew Wong

Patch series

Of 13 patch series (re-rolls counted once), 11 landed on master and 2 did not.

• not mergedMake git more user-friendly during a merge conflictMar 14, 2014
• mergedgit add -e: Explicitly specify that patch should have no colorJul 18, 2013, 7f3b8c628e
• mergedsetup.c: Fix prefix_pathspec from looping pass end of stringMar 9, 2013, f612a67eac
• mergedDocumentation/githooks: Fix linkgitMar 1, 2013, 5e2485846d
• mergedrebase: Handle cases where format-patch failsOct 11, 2012, e481af06be
• mergedgit-gui: Few issues with using full path nameOct 2, 2012, e3d06ca93e
• mergedRe: gitk: can't reload commits with new key bindingv2, Oct 2, 2012, 69ecfcd6eb
• mergedrebase -i: Teach "--edit-todo"v3, Sep 18, 2012, fcc5ef1cc9
• not mergedrebase -i: remove CHERRY_PICK_HEAD when cherry-pick failedMar 18, 2012
• mergedrebase -m: only call "notes copy" when rewritten exists and is non-emptyFeb 25, 2012, ad687b447a
• mergedrebase -i: interrupt rebase when "commit --amend" failed during "reword"Nov 30, 2011, 0becb3e4b9
• mergedInteractive-rebase doesn't pick all children of "upstream"v2, Jun 18, 2011, 12bf828348

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

• Feb 2, 2015"git status" should warn/error when it cannot lists a directory
• Jul 10, 2014Re: [PATCH RFC v2 01/19] rebase -i: Failed reword prints redundant error message
• Jul 10, 2014Re: [PATCH RFC v2 01/19] rebase -i: Failed reword prints redundant error message
• Mar 17, 2014Re: [PATCH 0/3] Make git more user-friendly during a merge conflict
• Mar 14, 2014Re: Apply commits from one branch to another branch (tree structure is different)
• Mar 14, 2014Re: [PATCH 3/3] reset: Print a warning when user uses "git reset" during a merge
• Mar 14, 2014Re: Apply commits from one branch to another branch (tree structure is different)
• Mar 14, 2014Re: Apply commits from one branch to another branch (tree structure is different)
• Mar 14, 2014Re: [PATCH 3/3] reset: Print a warning when user uses "git reset" during a merge
• Mar 14, 2014reset: Print a warning when user uses "git reset" during a merge
• Mar 14, 2014merge: Advise user to use "git merge --abort" to abort merges
• Mar 14, 2014wt-status: Make status messages more consistent with others
• Mar 14, 2014Make git more user-friendly during a merge conflict
• Mar 11, 2014Re: [RFC 3/3] reset: Change the default behavior to use "--merge" during a merge
• Mar 5, 2014Re: [RFC 2/3] merge: Add hints to tell users about "git merge --abort"
• Mar 5, 2014Re: [RFC 2/3] merge: Add hints to tell users about "git merge --abort"
• Feb 27, 2014Re: [RFC 3/3] reset: Change the default behavior to use "--merge" during a merge
• Feb 26, 2014Re: [RFC 3/3] reset: Change the default behavior to use "--merge" during a merge
• Feb 26, 2014Re: [RFC 2/3] merge: Add hints to tell users about "git merge --abort"
• Feb 26, 2014Re: [RFC 1/3] wt-status: Make conflict hint message more consistent with other hints
• Feb 26, 2014Re: [RFC 3/3] reset: Change the default behavior to use "--merge" during a merge
• Feb 26, 2014[RFC 3/3] reset: Change the default behavior to use "--merge" during a merge
• Feb 26, 2014[RFC 2/3] merge: Add hints to tell users about "git merge --abort"
• Feb 26, 2014[RFC 1/3] wt-status: Make conflict hint message more consistent with other hints
• Feb 26, 2014[RFC 0/3] Make git more user-friendly during a merge conflict
• Nov 28, 2013[RFC 3/3] git-svn: Add config to control the path of mergeinfo
• Nov 28, 2013[RFC 2/3] git-svn: Support cherry-pick merges
• Nov 28, 2013[RFC 1/3] git-svn: Generate mergeinfo for every commit
• Nov 28, 2013[RFC 0/3] git-svn: Add support for cherry-pick merges
• Jul 18, 2013git add -e: Explicitly specify that patch should have no color

Search their messages