All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Shawn O. Pearce" <spearce@spearce.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Randal L. Schwartz" <merlyn@stonehenge.com>, git@vger.kernel.org
Subject: Re: a475e8095aeb898c1ca60673b82df97d2300cc95 broken for docs
Date: Tue, 21 Aug 2007 21:41:40 -0400	[thread overview]
Message-ID: <20070822014140.GK27913@spearce.org> (raw)
In-Reply-To: <7v7inoo38o.fsf@gitster.siamese.dyndns.org>

Junio C Hamano <gitster@pobox.com> wrote:
> merlyn@stonehenge.com (Randal L. Schwartz) writes:
> 
> >>>>>> "Junio" == Junio C Hamano <gitster@pobox.com> writes:
> >
> > Junio> I think we've seen it reported that docbook-xsl 1.72 and/or 1.73
> > Junio> are broken.  Is your debug log from either of these versions?
> >
> > 1.71
> 
> Interesting.  I use 1.71 here too but it does not break.
> 
> I wonder what the differences are between our environments
> (don't answer that you use OSX and I use Debian and FC -- that
> much I already know).

It broke at day-job on Cygwin today.  I don't know what version
of docbook-xsl I'm using there.  But its fine on my OSX system.
I had planned on debugging it at home tonight, but I can't reproduce
it here.  Cute.  I will look at it again tomorrow and see if I can
debug the issue.

I'm pretty sure it was my recent edit to git-rev-list.txt; its
one of the only commits that has impacted that manual page since
the last time I had built that manual on Cygwin.  And no, nothing
else (e.g. docbook, asciidoc, xmlto) has changed since the last
successful build.

-- 
Shawn.

  reply	other threads:[~2007-08-22  1:41 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 [this message]
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

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=20070822014140.GK27913@spearce.org \
    --to=spearce@spearce.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --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.