From: Gustaf Hendeby <hendeby@isy.liu.se>
To: gitster@pobox.com
Cc: git@vger.kernel.org, Gustaf Hendeby <hendeby@isy.liu.se>
Subject: [PATCH] Documentation/user-manual.txt: fix typo
Date: Mon, 31 Dec 2007 14:31:35 +0100 [thread overview]
Message-ID: <1199107895-25950-1-git-send-email-hendeby@isy.liu.se> (raw)
In-Reply-To: <1198921945-25616-1-git-send-email-hendeby@isy.liu.se>
Signed-off-by: Gustaf Hendeby <hendeby@isy.liu.se>
---
I didn't see this one in the latest patches added to v1.5.4-rc2 so I
guess it was forgotten, or just dropped because it seems I forgot to
sign it the last time. (Sorry about that, it should teach me not to
do anything important at 4 in the morning...) I think the patch is
obviously correct so I'm resending.
/Gustaf
Documentation/user-manual.txt | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt
index f2b4206..3f552e9 100644
--- a/Documentation/user-manual.txt
+++ b/Documentation/user-manual.txt
@@ -74,7 +74,7 @@ version is called a <<def_commit,commit>>.
Those snapshots aren't necessarily all arranged in a single line from
oldest to newest; instead, work may simultaneously proceed along
-parallel lines of development, called <def_branch,branches>>, which may
+parallel lines of development, called <<def_branch,branches>>, which may
merge and diverge.
A single git repository can track development on multiple branches. It
--
1.5.4.rc2.8.g41c7c6
next prev parent reply other threads:[~2007-12-31 13:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-29 9:52 [PATCH] user-manual: fix typo Gustaf Hendeby
2007-12-31 13:31 ` Gustaf Hendeby [this message]
2007-12-31 16:28 ` [PATCH] Documentation/user-manual.txt: " J. Bruce Fields
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1199107895-25950-1-git-send-email-hendeby@isy.liu.se \
--to=hendeby@isy.liu.se \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).