From: Pierre Habouzit <madcoder@debian.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Documentation typo.
Date: Thu, 7 Jun 2007 00:18:06 +0200 [thread overview]
Message-ID: <20070606221806.GA23830@artemis> (raw)
In-Reply-To: <7v4plkzsuj.fsf@assigned-by-dhcp.cox.net>
[-- Attachment #1: Type: text/plain, Size: 2416 bytes --]
On Wed, Jun 06, 2007 at 02:16:36PM -0700, Junio C Hamano wrote:
> Pierre Habouzit <madcoder@debian.org> writes:
>
> > From: Pierre Habouzit <pierre.habouzit@m4x.org>
> >
> > Signed-off-by: Pierre Habouzit <madcoder@debian.org>
> > ---
> > Documentation/pull-fetch-param.txt | 2 +-
> > 1 files changed, 1 insertions(+), 1 deletions(-)
> >
> > diff --git a/Documentation/pull-fetch-param.txt b/Documentation/pull-fetch-param.txt
> > index 8d4e950..5bcdbc8 100644
> > --- a/Documentation/pull-fetch-param.txt
> > +++ b/Documentation/pull-fetch-param.txt
> > @@ -4,7 +4,7 @@
> >
> > <refspec>::
> > The canonical format of a <refspec> parameter is
> > - `+?<src>:<dst>`; that is, an optional plus `+`, followed
> > + `\+?<src>:<dst>`; that is, an optional plus `+`, followed
> > by the source ref, followed by a colon `:`, followed by
> > the destination ref.
> > +
>
> Not really. I suspect you are using AsciiDoc 8?
indeed ...
> Your patch does make AsciiDoc 8 keep '+' in the HTML output, but
> manual page output gets an extra backslash, so it is not really
> an improvement.
Not for me, using asciidoc 8.2.1 on debian. It was because the manpage
was missing a '+' that I actually wrote this patch, as it was really
akward.
> Unfortunately our documentation pages were written with AsciiDoc
> 7, and are not AsciiDoc 8 compatible.
>
> With -aasciidoc7compatible, AsciiDoc 8 is _supposed_ to behave
> compatibly, but in reality it does not format our documentation
> correctly. It certainly is possible that AsciiDoc 7 "happens to
> work" with our documentation pages, and maybe the way we abuse
> mark-ups can be argued the bug in _our_ documentation, but
> nobody on our end worked on finding a satisfactory solution to
> make our documentation format correctly with _both_ versions of
> AsciiDoc yet.
>
> I wrote about the differences between AsciiDoc 7, and AsciiDoc 8
> with the "compatiblity" I found a few weeks ago on this list;
> the most problematic was that 'asciidoc -aasciidoc7compatible'
> loses carets in our description where they matter X-<. The list
> archive may know more about the details,
Okay, I see, sorry for the noise then.
--
·O· Pierre Habouzit
··O madcoder@debian.org
OOO http://www.madism.org
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-06-06 22:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-05 22:25 [PATCH] Documentation typo Pierre Habouzit
2007-06-06 21:16 ` Junio C Hamano
2007-06-06 22:18 ` Pierre Habouzit [this message]
2007-06-07 2:09 ` Junio C Hamano
2007-06-15 6:34 ` [RFT] Format our Documentation/ with both AsciiDoc 7 & 8 Junio C Hamano
2007-06-15 8:09 ` Pierre Habouzit
2007-06-15 22:52 ` Junio C Hamano
2007-06-16 8:49 ` Pierre Habouzit
2007-06-16 21:05 ` Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2006-01-05 12:20 [PATCH] documentation typo Diego Calleja
2006-01-05 14:43 ` Bartlomiej Zolnierkiewicz
2006-01-13 16:10 ` Diego Calleja
2006-01-13 16:17 ` Bartlomiej Zolnierkiewicz
2006-01-15 22:24 ` Diego Calleja
2006-01-27 0:08 ` Diego Calleja
2006-01-27 0:36 ` Bartlomiej Zolnierkiewicz
2006-01-27 1:54 ` Diego Calleja
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=20070606221806.GA23830@artemis \
--to=madcoder@debian.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.