aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMattias Andrée <maandree@operamail.com>2013-09-19 17:37:18 +0200
committerMattias Andrée <maandree@operamail.com>2013-09-19 17:37:18 +0200
commitc39e302887a209f248eea17ca5f60c0bce5789d5 (patch)
tree098a07c1da159130fd349806e3905b67f5a0ce45
parenttypo (diff)
downloadusing-git-c39e302887a209f248eea17ca5f60c0bce5789d5.tar.gz
using-git-c39e302887a209f248eea17ca5f60c0bce5789d5.tar.bz2
using-git-c39e302887a209f248eea17ca5f60c0bce5789d5.tar.xz
grammaro
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 fe78da5..df8a690 100644
--- a/using-git.texinfo
+++ b/using-git.texinfo
@@ -630,7 +630,7 @@ will be printed by @command{git format-patch}.
Creating a patch this way will keep track
of the commit messages, and the individual
-commits. Another advantage with it is that
+commits. Another advantage with this is that
it can easily be submitted to a mailing list,
which the common way for large projects for
accepting patches.