Hi Paul, On 2015-05-18 17:06, Paul Tan wrote: > Since b10ac50 (Fix pulling into the same branch., 2005-08-25), git-pull, > upon detecting that git-fetch updated the current head, will > fast-forward the working tree to the updated head commit. This is just a quick note about something I noticed while reviewing: I was surprised that this code path would only trigger when `orig_head` is different from the null SHA-1, because in my mind, it is safe to update when we are on an unborn branch. However, I verified that the shell script does the same thing, so your transcription is faithful. Ciao, Dscho -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html