Is it, in fact, okay to fetch into the current branch if it's "yet to be
born"? I feel like it shouldn't be, since you'll get exactly the same
problem that you would if the branch already existed: the index reflects
the previous state (in this case, it's empty), so git will show that
you've staged removing all of the files, right? So this would make the
check for --update-head-ok more strict than before, but I think the
behavior change is correct.
-Daniel
*This .sig left intentionally blank*
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html