From: Junio C Hamano <gitster@pobox.com>
To: "Jason Sewall" <jasonsewall@gmail.com>
Cc: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>, git@vger.kernel.org
Subject: Re: [PATCH][RESEND] Escape some tilde characters causing spurious subscripts in documentation
Date: Sun, 24 Jun 2007 03:07:20 -0700 [thread overview]
Message-ID: <7vbqf5wtrb.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <31e9dd080706231722v760b5a0cnc31e24b83deafb90@mail.gmail.com> (Jason Sewall's message of "Sat, 23 Jun 2007 17:22:00 -0700")
"Jason Sewall" <jasonsewall@gmail.com> writes:
> On 6/23/07, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
>
>> I just checked with my copy of asciidoc, though, and there is no mangling
>> going on, at least in git-bundle.html (which is the only file I checked).
>> My asciidoc is version 8.2.1. What is yours?
>
> I've got 8.1.0; perhaps that's the problem. I wasn't so surprised to
> hear the asciidoc 7 and 8 don't get along, but I'm surprised to see
> that 8.1 and 8.2 are so different.
>
> Anyway, 8.1.0 is apparently what's in Fedora 7 (the distro I'm using
> right now) so it might be worth hanging on to the patch.
FWIW, 7.1.2, 8.2.1 and 7.0.2 all seem to be Ok (the last one is
used to format the pages in html and man branches of git.git).
It is a bit annoying having to use name\~num at some places and
no backslash all others.
Two requests:
- Documentation/git-rev-parse.txt has '{tilde}<n>'. If you
replace that {tilde} with a "~", how does your AsciiDoc
format it? Do you see the same breakage?
- If it breaks, does it fix the breakage if you prefix the "~"
with a backslash, instead of using {tilde}?
If the answer to both questions are "yes", then perhaps we
should get rid of the {tilde} macro we define in
Documentation/asciidoc.conf file, and use your "\~" solution
everywhere.
Also do you see any pattern? It does not seem that all the
"master~3" are broken for you but only some. If your commit
message can describe when quoting is needed, that would help
people who would modify the documentation in the future.
next prev parent reply other threads:[~2007-06-24 10:07 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 [this message]
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=7vbqf5wtrb.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).