All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Quy Tonthat <qtonthat@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Fix break in git-rev-list.txt
Date: Wed, 22 Aug 2007 03:01:44 -0700	[thread overview]
Message-ID: <7vbqczkhvb.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <11877706831306-git-send-email-qtonthat@gmail.com> (Quy Tonthat's message of "Wed, 22 Aug 2007 18:18:03 +1000")

Quy Tonthat <qtonthat@gmail.com> writes:

> diff --git a/Documentation/git-rev-list.txt b/Documentation/git-rev-list.txt
> index cbbc234..a0c611e 100644
> --- a/Documentation/git-rev-list.txt
> +++ b/Documentation/git-rev-list.txt
> @@ -298,8 +298,8 @@ used in the output.  When the starting commit is specified as
>  'commit@{now}', output also uses 'commit@\{timestamp}' notation
>  instead.  Under '\--pretty=oneline', the commit message is
>  prefixed with this information on the same line.
> -+
> -Cannot be combined with --reverse.
> +
> +Cannot be combined with '\--reverse'.

Hmph.  Interesting.  The text around this is:

	-g, --wark-reflogs::

        	Indented first paragraph...
	+
        With '\--pretty' fromat ... second paragraph ...
	prefixed with this information on the same line.
	+
        Cannot be combined with --reverse.

And its formatted form looks like either (without your patch):

	<listitem>
        <simpara>
        	Indented first paragraph...
	With <emphasis>--pretty</emphasis> format ...
	</simpara>
        <simpara>Cannot be combined with --reverse.</simpara>

        </listitem>	

or (with):

	<listitem>
        <simpara>
        	Indented first paragraph...
	With <emphasis>--pretty</emphasis> format ...
	Cannot be combined with --reverse.
	</simpara>

        </listitem>	

So it looks as if the only place that needs the ugly '+'
continuation marker is between the first and the second
paragraph.  And it also appears that the manpage backend does
not pay attention to the paragraph break there (HTML backend
places a <br /> before "With <em>--pretty</em>").

Is it just me, or the more we look at it, everybody doubts if
AsciiDoc was such a good choice?

It was a major plus that the input format is mostly readable as
straight text, but this was one of the sore points in our
formatting.  In the description part of a definition list, we
indent the first paragraph but append the second paragraph and
later with '+' without indenting (we would rather keep the
second and subsequent paragraphs aligned with the first one).
However, it appears that the definition has to be a single
paragraph and not any longer in such a list anyway.

Hmmmm.

In any case, I'd appreciate feedbacks from people who recently
reported formatting breakages on this patch.

  reply	other threads:[~2007-08-22 10:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-22  8:18 [PATCH] Fix break in git-rev-list.txt Quy Tonthat
2007-08-22 10:01 ` Junio C Hamano [this message]
2007-08-22 10:58   ` David Kastrup
2007-08-22 14:37   ` Quy Tonthat
2007-08-22 15:29   ` Quy Tonthat
2007-08-22 16:45   ` Quy Tonthat

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=7vbqczkhvb.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=qtonthat@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 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.