Junio C Hamano <gitster@xxxxxxxxx> wrote: > "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). Yea, most likely. Also I won't have any time in the near future to work on this implementation myself. I threw the idea out there in case someone else can find the time. I'm willing to do the work myself as I think its the right approach to use here for this update hook change, but I just don't see myself getting to it anytime before say Christmas... Its slightly more involved then what Steven originally proposed, but I think it solves the problem better and gives us more room for future improvements where we may want/need something such as a recursive ref locking. -- Shawn. - 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
