aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMattias Andrée <maandree@operamail.com>2015-04-08 22:33:10 +0200
committerMattias Andrée <maandree@operamail.com>2015-04-08 22:33:10 +0200
commitde66b143b1dafba5acb78de428cd86e16f33744d (patch)
tree895c1276c6e057aeaa4fbe7cc3a7f7f5efe354f3
parentgrammaro (diff)
downloadusing-git-de66b143b1dafba5acb78de428cd86e16f33744d.tar.gz
using-git-de66b143b1dafba5acb78de428cd86e16f33744d.tar.bz2
using-git-de66b143b1dafba5acb78de428cd86e16f33744d.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 b2d7a70..00e9d47 100644
--- a/using-git.texinfo
+++ b/using-git.texinfo
@@ -724,7 +724,7 @@ it can easily be submitted to a mailing list,
which the common way for large projects for
accepting patches.
-The created patch file is formated as an
+The created patch file is formatted as an
e-mail, with `[PATCH]' in the beginning of
the subject line. If you update the patch
it is customary to use `[PATCH v2]' instead