From: Junio C Hamano <junkio@cox.net>
To: Peter Hagervall <hager@cs.umu.se>
Cc: jdl@freescale.com, git@vger.kernel.org, junkio@cox.net
Subject: Re: PATCH Documentation/git-rev-list.txt typo fix
Date: Fri, 16 Sep 2005 09:31:42 -0700 [thread overview]
Message-ID: <7vy85xotxt.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20050916142412.GA973@brainysmurf.cs.umu.se> (Peter Hagervall's message of "Fri, 16 Sep 2005 16:24:12 +0200")
Peter Hagervall <hager@cs.umu.se> writes:
> This causes a mismatch in <emphasis> and <superscript> tags, one way of
> fixing it is having no more than one caret symbol per line, which is the
> only solution I found in the asciidoc documentation. Ugly, but it works.
Thanks.
Sigh...
next prev parent reply other threads:[~2005-09-16 16:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-15 22:40 PATCH Documentation/git-rev-list.txt typo fix jdl
2005-09-16 14:24 ` Peter Hagervall
2005-09-16 16:31 ` Junio C Hamano [this message]
2005-09-16 20:02 ` Chris Wright
2005-09-16 20:06 ` Chris Wright
2005-09-16 20:47 ` jdl
2005-09-16 23: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=7vy85xotxt.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=hager@cs.umu.se \
--cc=jdl@freescale.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).