| blob | 89c13b7e480d08a672ab4907d22c4d264654445f |
4 <head>
8 /* Debug borders */
10 /*
11 border: 1px solid red;
12 */
13 }
15 body {
17 }
19 a {
22 }
25 }
27 em {
29 }
31 strong {
33 }
35 tt {
37 }
45 }
49 }
50 h2 {
52 }
53 h3 {
55 }
56 h3 + * {
58 }
63 }
65 hr {
67 }
69 p {
72 }
74 pre {
77 }
79 span#author {
84 }
85 span#email {
86 }
87 span#revision {
89 }
91 div#footer {
97 }
98 div#footer-text {
101 }
102 div#footer-badges {
105 }
107 div#preamble,
114 }
118 }
122 }
124 /* Block element titles. */
131 }
134 }
138 }
141 }
144 }
150 }
154 }
159 }
163 }
167 }
170 }
179 }
183 }
188 }
192 }
198 dl {
201 }
202 dt {
206 }
209 }
213 }
216 }
220 }
221 thead {
224 }
225 tfoot {
227 }
232 }
235 }
240 }
243 }
247 }
249 div#toctitle {
256 }
261 }
265 }
269 }
273 }
275 /* Workarounds for IE6's broken and incomplete CSS2. */
281 }
287 }
293 }
297 }
302 }
304 /* IE6 sets dynamically generated links as visited. */
306 </style>
308 </head>
309 <body>
311 <h1>
312 git-update-ref(1) Manual Page
313 </h1>
316 <p>git-update-ref -
317 Update the object name stored in a ref safely
318 </p>
319 </div>
320 </div>
323 <div class="para"><p><em>git update-ref</em> [-m <reason>] (-d <ref> [<oldvalue>] | [--no-deref] <ref> <newvalue> [<oldvalue>])</p></div>
324 </div>
327 <div class="para"><p>Given two arguments, stores the <newvalue> in the <ref>, possibly
328 dereferencing the symbolic refs. E.g. <tt>git update-ref HEAD
331 possibly dereferencing the symbolic refs, after verifying that
337 not exist.</p></div>
339 ref file by starting with the four-byte header sequence of
342 these symbolic pointers, whether they are symlinks or these
344 if they start with "refs/": otherwise it will just try to read
345 them and update them as a regular file (i.e. it will allow the
346 filesystem to follow them, but will overwrite such a symlink to
347 somewhere else with a regular filename).</p></div>
349 the result of following the symbolic pointers.</p></div>
354 </div></div>
359 </div></div>
360 <div class="para"><p>both from a symlink following standpoint <strong>and</strong> an error checking
361 standpoint. The "refs/" rule for symlinks means that symlinks
362 that point to "outside" the tree are safe: they'll be followed
363 for reading but not for writing (so we'll never write through a
364 ref symlink to some other tree, if you have copied a whole
365 archive by creating a symlink tree).</p></div>
368 </div>
373 a line to the log file "$GIT_DIR/logs/<ref>" (dereferencing all
374 symbolic refs before creating the log name) describing the change
375 in ref value. Log lines are formatted as:</p></div>
377 <li>
378 <p>
379 oldsha1 SP newsha1 SP committer LF
380 </p>
384 and date in the standard GIT committer ident format.</p></div>
385 </li>
386 </ol></div>
389 <li>
390 <p>
391 oldsha1 SP newsha1 SP committer TAB message LF
392 </p>
394 value supplied to the -m option.</p></div>
395 </li>
396 </ol></div>
398 unable to create a new log file, append to the existing log file
399 or does not have committer information available.</p></div>
400 </div>
404 </div>
408 </div>
412 </div>
413 </div>
414 </body>
415 </html>