On Sun, 25 Sep 2005, Linus Torvalds wrote: > > This is a careful version of the script stuff that currently just > blindly writes HEAD with a new value. Btw, in case it wasn't clear from the patch, this only introduced mechanism, it didn't actually use it in any script. But the point of the exercise is to move towards using git-update-ref in places like git-fetch.sh, which currently are doing some of it by hand (and not handling symlinks etc). So you should be able to do something like .. old=$(git-rev-parse --verify "$refname^0") >& /dev/null if [ "$old" ]; then mb=$(git-merge-base $new $old) if [ "$mb" != "$old" ]; then echo "$new is not a fast-forward of $old" [ "$force" ] || exit 1 old= fi fi git-update-ref "$refname" $new $old and the actual update phase will re-verify that "old" is still valid (if it exists at all). Doing it by hand works, of course, but for example, if we have two symlinks pointing to the same ref, the current locking in git-fetch.sh is broken - it may lock the _symlink_, but since the other one _also_ points to the same thing, there's no locking of the _target_. git-update-ref should do things like that right. Famous last words ;) Linus - 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.htmlReceived on Mon Sep 26 05:07:19 2005
This archive was generated by hypermail 2.1.8 : 2005-09-26 05:07:21 EST