1 <?xml version="1.0" encoding="UTF-8"?>
\r
2 <!DOCTYPE sect2 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
\r
4 <sect2 lang="en" id="git-update-ref(1)">
\r
5 <title>git-update-ref(1)</title>
\r
7 <primary>git-update-ref(1)</primary>
\r
9 <simplesect id="git-update-ref(1)__name">
\r
11 <simpara>git-update-ref - Update the object name stored in a ref safely</simpara>
\r
13 <simplesect id="git-update-ref(1)__synopsis">
\r
14 <title>SYNOPSIS</title>
\r
16 <literallayout><emphasis>git update-ref</emphasis> [-m <reason>] (-d <ref> [<oldvalue>] | [--no-deref] <ref> <newvalue> [<oldvalue>])</literallayout>
\r
19 <simplesect id="git-update-ref(1)__description">
\r
20 <title>DESCRIPTION</title>
\r
21 <simpara>Given two arguments, stores the <newvalue> in the <ref>, possibly
\r
22 dereferencing the symbolic refs. E.g. <emphasis>git update-ref HEAD
\r
23 <newvalue></emphasis> updates the current branch head to the new object.</simpara>
\r
24 <simpara>Given three arguments, stores the <newvalue> in the <ref>,
\r
25 possibly dereferencing the symbolic refs, after verifying that
\r
26 the current value of the <ref> matches <oldvalue>.
\r
27 E.g. <emphasis>git update-ref refs/heads/master <newvalue> <oldvalue></emphasis>
\r
28 updates the master branch head to <newvalue> only if its current
\r
29 value is <oldvalue>. You can specify 40 "0" or an empty string
\r
30 as <oldvalue> to make sure that the ref you are creating does
\r
31 not exist.</simpara>
\r
32 <simpara>It also allows a "ref" file to be a symbolic pointer to another
\r
33 ref file by starting with the four-byte header sequence of
\r
35 <simpara>More importantly, it allows the update of a ref file to follow
\r
36 these symbolic pointers, whether they are symlinks or these
\r
37 "regular file symbolic refs". It follows <emphasis role="strong">real</emphasis> symlinks only
\r
38 if they start with "refs/": otherwise it will just try to read
\r
39 them and update them as a regular file (i.e. it will allow the
\r
40 filesystem to follow them, but will overwrite such a symlink to
\r
41 somewhere else with a regular filename).</simpara>
\r
42 <simpara>If --no-deref is given, <ref> itself is overwritten, rather than
\r
43 the result of following the symbolic pointers.</simpara>
\r
44 <simpara>In general, using</simpara>
\r
45 <literallayout class="monospaced">git update-ref HEAD "$head"</literallayout>
\r
46 <simpara>should be a <emphasis>lot</emphasis> safer than doing</simpara>
\r
47 <literallayout class="monospaced">echo "$head" > "$GIT_DIR/HEAD"</literallayout>
\r
48 <simpara>both from a symlink following standpoint <emphasis role="strong">and</emphasis> an error checking
\r
49 standpoint. The "refs/" rule for symlinks means that symlinks
\r
50 that point to "outside" the tree are safe: they'll be followed
\r
51 for reading but not for writing (so we'll never write through a
\r
52 ref symlink to some other tree, if you have copied a whole
\r
53 archive by creating a symlink tree).</simpara>
\r
54 <simpara>With <emphasis>-d</emphasis> flag, it deletes the named <ref> after verifying it
\r
55 still contains <oldvalue>.</simpara>
\r
57 <simplesect id="git-update-ref(1)__logging_updates">
\r
58 <title>Logging Updates</title>
\r
59 <simpara>If config parameter "core.logAllRefUpdates" is true and the ref is one under
\r
60 "refs/heads/", "refs/remotes/", "refs/notes/", or the symbolic ref HEAD; or
\r
61 the file "$GIT_DIR/logs/<ref>" exists then <emphasis>git update-ref</emphasis> will append
\r
62 a line to the log file "$GIT_DIR/logs/<ref>" (dereferencing all
\r
63 symbolic refs before creating the log name) describing the change
\r
64 in ref value. Log lines are formatted as:</simpara>
\r
65 <orderedlist numeration="arabic">
\r
68 oldsha1 SP newsha1 SP committer LF
\r
70 <simpara>Where "oldsha1" is the 40 character hexadecimal value previously
\r
71 stored in <ref>, "newsha1" is the 40 character hexadecimal value of
\r
72 <newvalue> and "committer" is the committer's name, email address
\r
73 and date in the standard GIT committer ident format.</simpara>
\r
76 <simpara>Optionally with -m:</simpara>
\r
77 <orderedlist numeration="arabic">
\r
80 oldsha1 SP newsha1 SP committer TAB message LF
\r
82 <simpara>Where all fields are as described above and "message" is the
\r
83 value supplied to the -m option.</simpara>
\r
86 <simpara>An update will fail (without changing <ref>) if the current user is
\r
87 unable to create a new log file, append to the existing log file
\r
88 or does not have committer information available.</simpara>
\r
90 <simplesect id="git-update-ref(1)__git">
\r
92 <simpara>Part of the <xref linkend="git(1)" /> suite</simpara>
\r