Autogenerated man pages for v1.2.4-gce5b6

[git.git] / man1 / git-update-ref.1

diff --git a/man1/git-update-ref.1 b/man1/git-update-ref.1
index ed1d730..fd4e3de 100755 (executable)
--- a/man1/git-update-ref.1
+++ b/man1/git-update-ref.1
@@ -23,7 +23,7 @@ git-update-ref \- update the object name stored in a ref safely
 .SH "SYNOPSIS"
 
 
-git\-update\-ref <ref> <newvalue> [<oldvalue>]
+\fIgit\-update\-ref\fR <ref> <newvalue> [<oldvalue>]
 
 .SH "DESCRIPTION"
 
@@ -37,7 +37,7 @@ Given three arguments, stores the <newvalue> in the <ref>, possibly dereferencin
 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)\&.
+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
@@ -54,7 +54,7 @@ echo "$head" > "$GIT_DIR/HEAD"
 .fi
 
 
-both from a symlink following standpoint and 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)\&.
+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"