From: "Karl Hasselström" <kha@treskal.com>
To: Junio C Hamano <junkio@cox.net>
Cc: Eric Wong <normalperson@yhbt.net>, git@vger.kernel.org
Subject: Re: [git-svn PATCH] Fix markup in git-svn man page
Date: Sat, 5 May 2007 15:02:17 +0200 [thread overview]
Message-ID: <20070505130217.GA3379@diana.vm.bytemark.co.uk> (raw)
In-Reply-To: <7vslacs0p6.fsf@assigned-by-dhcp.cox.net>
On 2007-05-04 15:06:45 -0700, Junio C Hamano wrote:
> Looks sane to me. I did not know about double-semicolon, which is
> mentioned in the user guide documentation at the asciidoc site but I
> could not tell how it is different from double-colon form. I am
> guessing (from the behaviour after applying your patch) that it
> allows second level of listing...
Yes, it was used that way in the parts of the man page that already
looked OK, so I just copied it. If it looks good to you too, it must
be correct. :-)
--
Karl Hasselström, kha@treskal.com
www.treskal.com/kalle
prev parent reply other threads:[~2007-05-05 17:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-04 7:03 [git-svn PATCH] Fix markup in git-svn man page Karl Hasselström
2007-05-04 8:06 ` Eric Wong
2007-05-04 22:06 ` Junio C Hamano
2007-05-05 13:02 ` Karl Hasselström [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=20070505130217.GA3379@diana.vm.bytemark.co.uk \
--to=kha@treskal.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=normalperson@yhbt.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).