All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: merlyn@stonehenge.com (Randal L. Schwartz)
Cc: git@vger.kernel.org
Subject: Re: a475e8095aeb898c1ca60673b82df97d2300cc95 broken for docs
Date: Wed, 22 Aug 2007 12:45:28 -0700	[thread overview]
Message-ID: <7vveb7ic9z.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <86odgzmx2z.fsf@blue.stonehenge.com> (Randal L. Schwartz's message of "Wed, 22 Aug 2007 08:02:28 -0700")

Thanks.  One difference we overlooked was the differences in
versions of AsciiDoc; Quy sees problem with 8 while I do not
with 7 (both my private machine and k.org machine -- the latter
of which is where preformatted documentation pages in html and
man branches come from).  I think Shawn was correct to pinpoint
that exact change as the culprit and Quy Tonthat is on the right
track, with this patch...



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'.
 
 --merge::
 
@@ -375,7 +375,7 @@ By default, the commits are shown in reverse chronological order.
 --reverse::
 
 	Output the commits in reverse order.
-	Cannot be combined with --walk-reflogs.
+	Cannot be combined with '\--walk-reflogs'.
 
 Object Traversal
 ~~~~~~~~~~~~~~~~

      reply	other threads:[~2007-08-22 19:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-21 17:51 a475e8095aeb898c1ca60673b82df97d2300cc95 broken for docs Randal L. Schwartz
2007-08-21 21:15 ` Junio C Hamano
2007-08-21 21:37   ` Randal L. Schwartz
2007-08-21 23:51     ` Junio C Hamano
2007-08-22  1:41       ` Shawn O. Pearce
2007-08-22  5:09         ` David Kastrup
2007-08-22  7:24         ` David Kastrup
2007-08-21 21:45   ` Mike Hommey
2007-08-22  8:13 ` Junio C Hamano
2007-08-22 15:02   ` Randal L. Schwartz
2007-08-22 19:45     ` Junio C Hamano [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=7vveb7ic9z.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=merlyn@stonehenge.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.