From: Michael J Gruber <git@drmicha.warpmail.net>
To: Jay Soffian <jaysoffian@gmail.com>
Cc: Tom Holaday <tlholaday@gmail.com>, git@vger.kernel.org
Subject: Re: git doc build failure on OS X 10.5.6 (Leopard) during xmlto phase
Date: Wed, 11 Mar 2009 17:27:28 +0100 [thread overview]
Message-ID: <49B7E670.7060606@drmicha.warpmail.net> (raw)
In-Reply-To: <76718490903110849x2ef48a89j3f17706390991eda@mail.gmail.com>
Jay Soffian venit, vidit, dixit 11.03.2009 16:49:
> On Wed, Mar 11, 2009 at 11:39 AM, Jay Soffian <jaysoffian@gmail.com> wrote:
>> On Wed, Mar 11, 2009 at 11:12 AM, Jay Soffian <jaysoffian@gmail.com> wrote:
>>> And your man pages still won't be perfect. Preformatted text will look
>>> like this:
>>>
>>> .ft C
>>> ...
>>> .ft
> I must be losing my mind. This is suddenly working, though I can't
> track it down to any change in git. I just rebuilt my man pages and
> this no longer is occurring, even though I still have a terminal
> window open with the output of "git help help" _showing this problem_
> and that's from man pages I built/installed just a few days ago. (And
> I haven't upgraded MacPorts lately.)
>
> Oh well.
>
> j.
FWIW: The effect you describe (which is different from the OP) occurs on
Fedora 10 as well, and not only for git man pages, also for others. I've
been meaning to look into this, just like I've been meaning to look into
so much stuff...
Michael
next prev parent reply other threads:[~2009-03-11 16:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-11 14:21 git doc build failure on OS X 10.5.6 (Leopard) during xmlto phase Tom Holaday
2009-03-11 14:43 ` Michael J Gruber
2009-03-11 15:12 ` Jay Soffian
2009-03-11 15:39 ` Jay Soffian
2009-03-11 15:49 ` Jay Soffian
2009-03-11 16:27 ` Michael J Gruber [this message]
2009-03-11 20:12 ` Alejandro Riveira
2009-03-12 11:17 ` Michael J Gruber
2009-03-12 14:02 ` Alejandro Riveira Fernández
2009-03-12 17:09 ` Todd Zullinger
2009-03-13 10:29 ` Michael J Gruber
2009-03-13 16:18 ` Jay Soffian
2009-03-13 17:06 ` Michael J Gruber
2009-03-31 20:17 ` byrnejb
2009-03-31 20:56 ` byrnejb
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=49B7E670.7060606@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=jaysoffian@gmail.com \
--cc=tlholaday@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 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).