From: bfields@fieldses.org
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: [PATCH 5/5] Documentation: fix a tutorial-2 typo
Date: Mon, 29 May 2006 19:31:36 -0400 [thread overview]
Message-ID: <11489454963791-git-send-email-bfields@fieldses.org> (raw)
In-Reply-To: <11489454963586-git-send-email-bfields@fieldses.org>
From: J. Bruce Fields <bfields@citi.umich.edu>
Fix a typo.
Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu>
---
2506b48d2aee595a5023d31166a64d4d28bf8789
Documentation/tutorial-2.txt | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
2506b48d2aee595a5023d31166a64d4d28bf8789
diff --git a/Documentation/tutorial-2.txt b/Documentation/tutorial-2.txt
index 08d3453..9c9500c 100644
--- a/Documentation/tutorial-2.txt
+++ b/Documentation/tutorial-2.txt
@@ -377,7 +377,7 @@ At this point you should know everything
pages for any of the git commands; one good place to start would be
with the commands mentioned in link:everyday.html[Everyday git]. You
should be able to find any unknown jargon in the
-link:glossary.html[Glosssay].
+link:glossary.html[Glossary].
The link:cvs-migration.html[CVS migration] document explains how to
import a CVS repository into git, and shows how to use git in a
--
1.3.3.gff62
prev parent reply other threads:[~2006-05-29 23:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-29 23:31 [PATCH 1/5] documentation: mention gitk font adjustment in tutorial bfields
2006-05-29 23:31 ` [PATCH 2/5] documentation: add brief mention of cat-file to tutorial part I bfields
2006-05-29 23:31 ` [PATCH 3/5] Documentation: retitle the git-core tutorial bfields
2006-05-29 23:31 ` [PATCH 4/5] Documentation: rewrite the core-tutorial introduction bfields
2006-05-29 23:31 ` bfields [this message]
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=11489454963791-git-send-email-bfields@fieldses.org \
--to=bfields@fieldses.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).