From: Johan Herland <johan@herland.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Gustaf Hendeby <hendeby@isy.liu.se>
Subject: Re: [PATCH] Fix AsciiDoc errors in merge documentation
Date: Fri, 05 Sep 2008 08:09:20 +0200 [thread overview]
Message-ID: <200809050809.20791.johan@herland.net> (raw)
In-Reply-To: <7vbpz31oup.fsf@gitster.siamese.dyndns.org>
On Friday 05 September 2008, Junio C Hamano wrote:
> Johan Herland <johan@herland.net> writes:
> > [...]
>
> Thanks. It's good to see issues with new changes are resolved while they
> are still in 'next'.
Hey, that's what next is for, isn't it? ;)
> Have you tried this patch without double quotes around the teletype text,
> by the way?
Seems to work fine, as well.
...Johan
--
Johan Herland, <johan@herland.net>
www.herland.net
prev parent reply other threads:[~2008-09-05 6:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-04 10:43 [BUG] Problem compiling documentation Gustaf Hendeby
2008-09-04 21:48 ` [PATCH] Fix AsciiDoc errors in merge documentation Johan Herland
2008-09-04 22:26 ` Gustaf Hendeby
2008-09-04 23:19 ` Junio C Hamano
2008-09-05 6:09 ` Johan Herland [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=200809050809.20791.johan@herland.net \
--to=johan@herland.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=hendeby@isy.liu.se \
/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).