git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jason Sewall <jasonsewall@gmail.com>
Cc: gitster@pobox.com, Johannes.Schindelin@gmx.de, git@vger.kernel.org
Subject: Re: [PATCH][RESEND] Escape some tilde characters causing spurious subscripts in documentation
Date: Sat, 23 Jun 2007 18:01:36 -0700	[thread overview]
Message-ID: <7vhcoy2mj3.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <11826426733115-git-send-email-jasonsewall@gmail.com> (Jason Sewall's message of "Sat, 23 Jun 2007 16:51:13 -0700")

Jason Sewall <jasonsewall@gmail.com> writes:

> 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

We seem to have {tilde} defined in Documentation/asciidoc.conf.
I wonder which is better.  We should pick one that gives more
reasonable format, and is less susceptible to differences
between AsciiDoc 7 and 8.

      parent reply	other threads:[~2007-06-24  1:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-23 23:51 [PATCH][RESEND] Escape some tilde characters causing spurious subscripts in documentation Jason Sewall
2007-06-24  0:11 ` 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 [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=7vhcoy2mj3.fsf@assigned-by-dhcp.cox.net \
    --to=gitster@pobox.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=jasonsewall@gmail.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).