aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMattias Andrée <maandree@operamail.com>2013-09-19 18:17:07 +0200
committerMattias Andrée <maandree@operamail.com>2013-09-19 18:17:07 +0200
commit1f5243f17aa6b741815830fbd2216be6cfd60f7b (patch)
tree2f28a8396f81627aa73d7a96985b6d7d08a733f2
parenttypo (diff)
downloadusing-git-1f5243f17aa6b741815830fbd2216be6cfd60f7b.tar.gz
using-git-1f5243f17aa6b741815830fbd2216be6cfd60f7b.tar.bz2
using-git-1f5243f17aa6b741815830fbd2216be6cfd60f7b.tar.xz
typo
Signed-off-by: Mattias Andrée <maandree@operamail.com>
-rw-r--r--using-git.texinfo4
1 files changed, 2 insertions, 2 deletions
diff --git a/using-git.texinfo b/using-git.texinfo
index 81a207f..6cb454d 100644
--- a/using-git.texinfo
+++ b/using-git.texinfo
@@ -1404,8 +1404,8 @@ to perserve the modification time. If you
have compiled the program, and then checkout
an earlier commit, perhaps another branch,
and you build it again, now your compiled
-files from the other branch has a newer time
-stamp then the source in the current branch
+files from the other branch has a newer
+timestamp then the source in the current branch
and the files will not build unless you
force them to build, which you more than
likely will forget. So you may observe a