aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMattias Andrée <maandree@operamail.com>2013-09-19 18:16:06 +0200
committerMattias Andrée <maandree@operamail.com>2013-09-19 18:16:06 +0200
commitf2078017bdad5b359cd041811c908dcb63f1877e (patch)
treee5604b897199baf5b947245c7a9943d11a151a47
parentm (diff)
downloadusing-git-f2078017bdad5b359cd041811c908dcb63f1877e.tar.gz
using-git-f2078017bdad5b359cd041811c908dcb63f1877e.tar.bz2
using-git-f2078017bdad5b359cd041811c908dcb63f1877e.tar.xz
typo
Signed-off-by: Mattias Andrée <maandree@operamail.com>
-rw-r--r--using-git.texinfo2
1 files changed, 1 insertions, 1 deletions
diff --git a/using-git.texinfo b/using-git.texinfo
index d35001a..81a207f 100644
--- a/using-git.texinfo
+++ b/using-git.texinfo
@@ -1402,7 +1402,7 @@ Perserving modification time on files is
considered harmful. Consider if Git were
to perserve the modification time. If you
have compiled the program, and then checkout
-en earlier commit, perhaps another branch,
+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