| blob | 3b1afbb1d427eb02075cc9d495d58d01aeae273e |
4 <head>
9 /* Debug borders */
11 /*
12 border: 1px solid red;
13 */
14 }
16 body {
18 }
20 a {
23 }
26 }
28 em {
31 }
33 strong {
36 }
38 tt {
40 }
48 }
52 }
53 h2 {
55 }
56 h3 {
58 }
59 h3 + * {
61 }
66 }
68 hr {
70 }
72 p {
75 }
79 }
81 pre {
84 }
86 span#author {
91 }
92 span#email {
93 }
96 }
98 div#footer {
104 }
105 div#footer-text {
108 }
109 div#footer-badges {
112 }
114 div#preamble {
117 }
123 }
127 }
131 }
133 /* Block element titles. */
141 }
144 }
148 }
151 }
154 }
160 }
166 }
171 }
175 }
180 }
183 }
187 }
188 /* DEPRECATED: Pre version 8.2.7 verse style literal block. */
191 }
200 }
204 }
209 }
215 dl {
218 }
219 dt {
224 }
227 }
231 }
234 }
237 }
240 }
243 }
246 }
253 }
257 }
258 thead {
261 }
262 tfoot {
264 }
267 }
270 }
271 /* Because the table frame attribute is overriden by CSS in most browsers. */
274 }
278 }
282 }
288 }
291 }
294 }
300 }
303 }
307 }
311 }
315 }
317 div#toctitle {
324 }
329 }
333 }
337 }
341 }
342 /* Overrides for manpage documents */
343 h1 {
348 }
349 h2 {
351 }
354 }
358 }
360 /* Workarounds for IE6's broken and incomplete CSS2. */
366 }
373 }
379 }
384 }
388 }
392 }
397 }
399 /* IE6 sets dynamically generated links as visited. */
401 </style>
402 </head>
403 <body>
405 <h1>
406 git-update-ref(1) Manual Page
407 </h1>
410 <p>git-update-ref -
411 Update the object name stored in a ref safely
412 </p>
413 </div>
414 </div>
418 <div class="verseblock-content"><em>git update-ref</em> [-m <reason>] (-d <ref> [<oldvalue>] | [--no-deref] <ref> <newvalue> [<oldvalue>])</div>
420 </div></div>
421 </div>
424 <div class="paragraph"><p>Given two arguments, stores the <newvalue> in the <ref>, possibly
425 dereferencing the symbolic refs. E.g. <tt>git update-ref HEAD
427 <div class="paragraph"><p>Given three arguments, stores the <newvalue> in the <ref>,
428 possibly dereferencing the symbolic refs, after verifying that
434 not exist.</p></div>
436 ref file by starting with the four-byte header sequence of
439 these symbolic pointers, whether they are symlinks or these
441 if they start with "refs/": otherwise it will just try to read
442 them and update them as a regular file (i.e. it will allow the
443 filesystem to follow them, but will overwrite such a symlink to
444 somewhere else with a regular filename).</p></div>
445 <div class="paragraph"><p>If --no-deref is given, <ref> itself is overwritten, rather than
446 the result of following the symbolic pointers.</p></div>
451 </div></div>
456 </div></div>
457 <div class="paragraph"><p>both from a symlink following standpoint <strong>and</strong> an error checking
458 standpoint. The "refs/" rule for symlinks means that symlinks
460 for reading but not for writing (so we’ll never write through a
461 ref symlink to some other tree, if you have copied a whole
462 archive by creating a symlink tree).</p></div>
463 <div class="paragraph"><p>With <tt>-d</tt> flag, it deletes the named <ref> after verifying it
465 </div>
468 <div class="paragraph"><p>If config parameter "core.logAllRefUpdates" is true and the ref is one under
471 a line to the log file "$GIT_DIR/logs/<ref>" (dereferencing all
472 symbolic refs before creating the log name) describing the change
473 in ref value. Log lines are formatted as:</p></div>
475 <li>
476 <p>
477 oldsha1 SP newsha1 SP committer LF
478 </p>
482 and date in the standard GIT committer ident format.</p></div>
483 </li>
484 </ol></div>
487 <li>
488 <p>
489 oldsha1 SP newsha1 SP committer TAB message LF
490 </p>
492 value supplied to the -m option.</p></div>
493 </li>
494 </ol></div>
495 <div class="paragraph"><p>An update will fail (without changing <ref>) if the current user is
496 unable to create a new log file, append to the existing log file
497 or does not have committer information available.</p></div>
498 </div>
502 </div>
506 </div>
507 </div>
508 </body>
509 </html>