Kevin Green

Patch series

Of 3 patch series (re-rolls counted once), 0 landed on master and 3 did not.

• not mergedgit-p4: Fix race between p4_edit and p4_changeApr 3, 2008
• not mergedFix assumption that git is installed in a standard place on the remote end sshJun 15, 2007
• not mergedgit-p4: check for existence of repo dir before trying to create [Was: Asking again... [Re: how to properly import perforce history?]]Jun 11, 2007

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 24, 2010confusion over git-cherry-pick, git-merge and git-cherry
• Aug 11, 2009Re: rename/copy detection not working for git-log?
• Aug 11, 2009rename/copy detection not working for git-log?
• Oct 9, 2008Re: keeping remote branches in sync
• Oct 9, 2008keeping remote branches in sync
• Apr 11, 2008Re: [PATCH] git-p4: Work around race between p4_edit and p4_change
• Apr 3, 2008git-p4: Work around race between p4_edit and p4_change
• Apr 3, 2008Re: [PATCH] git-p4: Fix race between p4_edit and p4_change
• Apr 1, 2008git-p4: Fix race between p4_edit and p4_change
• Jun 22, 2007Re: [RFC][PATCH] Fix assumption that git is installed in a standard place on the remote end ssh
• Jun 15, 2007Re: [RFC][PATCH] Fix assumption that git is installed in a standard place on the remote end ssh
• Jun 15, 2007Fix assumption that git is installed in a standard place on the remote end ssh
• Jun 11, 2007git-p4: check for existence of repo dir before trying to create [Was: Asking again... [Re: how to properly import perforce history?]]
• Jun 11, 2007Re: Asking again... [Re: how to properly import perforce history?]
• Jun 11, 2007Asking again... [Re: how to properly import perforce history?]
• Jun 8, 2007how to properly import perforce history...
• Jun 7, 2007Re: pull/merge --no-commit

Search their messages