.\"Generated by db2man.xsl. Don't modify this, modify the source. .de Sh \" Subsection .br .if t .Sp .ne 5 .PP \fB\\$1\fR .PP .. .de Sp \" Vertical space (when we can't use .PP) .if t .sp .5v .if n .sp .. .de Ip \" List item .br .ie \\n(.$>=3 .ne \\$3 .el .ne 3 .IP "\\$1" \\$2 .. .TH "GIT-UPDATE-REF" 1 "" "" "" .SH NAME git-update-ref \- update the object name stored in a ref safely .SH "SYNOPSIS" \fIgit\-update\-ref\fR [] .SH "DESCRIPTION" Given two arguments, stores the in the , possibly dereferencing the symbolic refs\&. E\&.g\&. git\-update\-ref HEAD updates the current branch head to the new object\&. Given three arguments, stores the in the , possibly dereferencing the symbolic refs, after verifying that the current value of the matches \&. E\&.g\&. git\-update\-ref refs/heads/master updates the master branch head to only if its current value is \&. It also allows a "ref" file to be a symbolic pointer to another ref file by starting with the four\-byte header sequence of "ref:"\&. More importantly, it allows the update of a ref file to follow these symbolic pointers, whether they are symlinks or these "regular file symbolic refs"\&. It follows \fIreal\fR symlinks only if they start with "refs/": otherwise it will just try to read them and update them as a regular file (i\&.e\&. it will allow the filesystem to follow them, but will overwrite such a symlink to somewhere else with a regular filename)\&. In general, using .nf git\-update\-ref HEAD "$head" .fi should be a _lot_ safer than doing .nf echo "$head" > "$GIT_DIR/HEAD" .fi both from a symlink following standpoint \fIand\fR an error checking standpoint\&. The "refs/" rule for symlinks means that symlinks that point to "outside" the tree are safe: they'll be followed for reading but not for writing (so we'll never write through a ref symlink to some other tree, if you have copied a whole archive by creating a symlink tree)\&. .SH "AUTHOR" Written by Linus Torvalds \&. .SH "GIT" Part of the \fBgit\fR(7) suite