"Shawn O. Pearce" <spearce@xxxxxxxxxxx> writes: > This probably requires exporting the name of the ref we currently > have locked in an environment variable (and teach lockfile.c it) > so we can effectively do recursive locking. That way the update > hook can still use git-update-ref to change the ref safely. Heh, I like that, although I suspect getting this right would mean the topic should be post 1.5.4 (which I do not mind). - 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
