Rechercher une page de manuel
git-update-ref
Langue: en
Version: 09/23/2007 (openSuse - 09/10/07)
Section: 1 (Commandes utilisateur)
NAME
git-update-ref - Update the object name stored in a ref safelySYNOPSIS
git-update-ref [-m <reason>] (-d <ref> <oldvalue> | <ref> <newvalue> [<oldvalue>])DESCRIPTION
Given two arguments, stores the <newvalue> in the <ref>, possibly dereferencing the symbolic refs. E.g. git-update-ref HEAD <newvalue> updates the current branch head to the new object.Given three arguments, stores the <newvalue> in the <ref>, possibly dereferencing the symbolic refs, after verifying that the current value of the <ref> matches <oldvalue>. E.g. git-update-ref refs/heads/master <newvalue> <oldvalue> updates the master branch head to <newvalue> only if its current value is <oldvalue>. You can specify 40 "0" or an empty string as <oldvalue> to make sure that the ref you are creating does not exist.
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 real 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
-
git-update-ref HEAD "$head"
-
echo "$head" > "$GIT_DIR/HEAD"
With -d flag, it deletes the named <ref> after verifying it still contains <oldvalue>.
LOGGING UPDATES
If config parameter "core.logAllRefUpdates" is true or the file "$GIT_DIR/logs/<ref>" exists then git-update-ref will append a line to the log file "$GIT_DIR/logs/<ref>" (dereferencing all symbolic refs before creating the log name) describing the change in ref value. Log lines are formatted as:- 1.oldsha1 SP newsha1 SP committer LF
Where "oldsha1" is the 40 character hexadecimal value previously stored in <ref>, "newsha1" is the 40 character hexadecimal value of <newvalue> and "committer" is the committer's name, email address and date in the standard GIT committer ident format.
- 1.oldsha1 SP newsha1 SP committer TAB message LF
Where all fields are as described above and "message" is the value supplied to the -m option.
AUTHOR
Written by Linus Torvalds <torvalds@osdl.org>.GIT
Part of the git(7) suiteContenus ©2006-2024 Benjamin Poulain
Design ©2006-2024 Maxime Vantorre