From: Jason Sewall <jasonsewall@gmail.com>
To: gitster@pobox.com, Johannes.Schindelin@gmx.de, git@vger.kernel.org
Cc: Jason Sewall <jasonsewall@gmail.com>
Subject: [PATCH][RESEND] Escape some tilde characters causing spurious subscripts in documentation
Date: Sat, 23 Jun 2007 16:51:13 -0700 [thread overview]
Message-ID: <11826426733115-git-send-email-jasonsewall@gmail.com> (raw)
A few unescaped tilde characters were causing long parts of the html documentation to be formatted as footnotes. This patch fixes them; I think I found all of them, but no promises.
Signed-off-by: Jason Sewall <jasonsewall@gmail.com>
---
My second attempt at submitting a patch, this time with git-send-email rather than copy-and-paste into gmail; let me know if this is a reasonably presented patch. It is truly trivial, but getting those docs cleaned up is important!
Documentation/git-bundle.txt | 8 ++++----
Documentation/git-daemon.txt | 2 +-
2 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/Documentation/git-bundle.txt b/Documentation/git-bundle.txt
index 5051e2b..d89f350 100644
--- a/Documentation/git-bundle.txt
+++ b/Documentation/git-bundle.txt
@@ -61,7 +61,7 @@ unbundle <file>::
[git-rev-list-args...]::
A list of arguments, acceptable to git-rev-parse and
git-rev-list, that specify the specific objects and references
- to transport. For example, "master~10..master" causes the
+ to transport. For example, "master\~10..master" causes the
current master reference to be packaged along with all objects
added since its 10th ancestor commit. There is no explicit
limit to the number of references and objects that may be
@@ -80,12 +80,12 @@ SPECIFYING REFERENCES
git-bundle will only package references that are shown by
git-show-ref: this includes heads, tags, and remote heads. References
-such as master~1 cannot be packaged, but are perfectly suitable for
+such as master\~1 cannot be packaged, but are perfectly suitable for
defining the basis. More than one reference may be packaged, and more
than one basis can be specified. The objects packaged are those not
contained in the union of the given bases. Each basis can be
-specified explicitly (e.g., ^master~10), or implicitly (e.g.,
-master~10..master, master --since=10.days.ago).
+specified explicitly (e.g., ^master\~10), or implicitly (e.g.,
+master\~10..master, master --since=10.days.ago).
It is very important that the basis used be held by the destination.
It is okay to err on the side of conservatism, causing the bundle file
diff --git a/Documentation/git-daemon.txt b/Documentation/git-daemon.txt
index 4b30b18..3f9cec5 100644
--- a/Documentation/git-daemon.txt
+++ b/Documentation/git-daemon.txt
@@ -98,7 +98,7 @@ OPTIONS
--verbose, thus by default only error conditions will be logged.
--user-path, --user-path=path::
- Allow ~user notation to be used in requests. When
+ Allow \~user notation to be used in requests. When
specified with no parameter, requests to
git://host/~alice/foo is taken as a request to access
'foo' repository in the home directory of user `alice`.
--
1.5.2.1.280.g38570
next reply other threads:[~2007-06-23 23:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-23 23:51 Jason Sewall [this message]
2007-06-24 0:11 ` [PATCH][RESEND] Escape some tilde characters causing spurious subscripts in documentation Johannes Schindelin
2007-06-24 0:22 ` Jason Sewall
2007-06-24 0:55 ` Johannes Schindelin
2007-06-24 10:07 ` Junio C Hamano
2007-06-24 17:31 ` Jason Sewall
2007-06-24 21:40 ` Jason Sewall
2007-06-24 22:18 ` Junio C Hamano
2007-06-24 23:33 ` Jason Sewall
2007-06-24 1:01 ` Junio C Hamano
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=11826426733115-git-send-email-jasonsewall@gmail.com \
--to=jasonsewall@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--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).