From: Andrew Ruder <andy@aeruder.net>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: [PATCH] Fix unmatched emphasis tag in git-tutorial
Date: Wed, 18 Apr 2007 22:03:31 -0500 [thread overview]
Message-ID: <20070419030331.GC19402@bowser.ruder> (raw)
In-Reply-To: <20070416053525.GA18821@localdomain>
In asciidoc 7.1.2 and prior there is no obvious way to get:
'add'ing
to emphasize only the "add", instead it treats the first apostrophe as the
beginning of an emphasis, and the second apostrophe as a regular
apostrophe and makes the rest of the line an emphasis since there is no
closing apostrophe. In the newer asciidoc you can do it pretty easily
with __add__ing but I'm not sure it would be best to make that a prereq
for something as silly as this.
Signed-off-by: Andrew Ruder <andy@aeruder.net>
---
Documentation/tutorial.txt | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/Documentation/tutorial.txt b/Documentation/tutorial.txt
index 129c5c5..e978562 100644
--- a/Documentation/tutorial.txt
+++ b/Documentation/tutorial.txt
@@ -111,7 +111,7 @@ make it real.
Note: don't forget to 'add' a file again if you modified it after the
first 'add' and before 'commit'. Otherwise only the previous added
state of that file will be committed. This is because git tracks
-content, so what you're really 'add'ing to the commit is the *content*
+content, so what you're really 'adding' to the commit is the *content*
of the file in the state it is in when you 'add' it.
2) By using 'git commit -a' directly
--
1.5.1.1.116.g8c4c
next prev parent reply other threads:[~2007-04-19 3:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-16 5:35 [PATCH] Add policy on user-interface changes Andrew Ruder
2007-04-16 6:20 ` [PATCH] Update git-am documentation Andrew Ruder
2007-04-16 6:56 ` Junio C Hamano
2007-04-16 7:21 ` Andrew Ruder
2007-04-16 7:48 ` Junio C Hamano
2007-04-16 12:47 ` Andrew Ruder
2007-04-16 6:20 ` [PATCH] Update git-applymbox documentation Andrew Ruder
2007-04-16 6:40 ` Andrew Ruder
2007-04-16 6:20 ` [PATCH] Update git-annotate/git-blame documentation Andrew Ruder
2007-04-16 7:24 ` Alex Riesen
2007-04-16 7:26 ` Andrew Ruder
2007-04-16 7:52 ` Junio C Hamano
2007-04-17 2:45 ` Andrew Ruder
2007-04-16 6:20 ` [PATCH] Update git-apply documentation Andrew Ruder
2007-04-19 3:03 ` [PATCH] Update git-archive documentation Andrew Ruder
2007-04-19 3:03 ` [PATCH] Update git-cherry-pick documentation Andrew Ruder
2007-04-19 3:03 ` Andrew Ruder [this message]
2007-04-19 3:03 ` [PATCH] Update git-config documentation Andrew Ruder
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=20070419030331.GC19402@bowser.ruder \
--to=andy@aeruder.net \
--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).