We have two branches in Git, master and develop . master constantly updated by a group of partners, and I constantly switch the develop branch to master , something like this:
#(on develop) $ git pull --rebase origin master
... but yesterday someone from the partner group on master did not provide a proper email address, so I ran into a problem in step #2 :
git rebase origin/develop First, rewinding head to replay your work on top of it... Applying: <...> <...> Patch does not have a valid e-mail address.
and git status shows:
$ git status
What I did was skip commits without an address using git rebase --skip , and then cherry-pick them after recovery. But I think this is the right way to do this? Can I make a cherry grab on the spot without missing it? If so, how do I really recognize this problematic commit (without looking into git log ), since this is basically the next commit that needs to be reinstalled at the top of the current commit, so git must somehow know which one ... ?
source share