From: Michael J Gruber <git@drmicha•warpmail.net>
To: Saikiran Madugula <hummerbliss@gmail•com>
Cc: Thomas Rast <trast@student•ethz.ch>, git@vger•kernel.org
Subject: Re: [PATCH] Documentation: Fix build failure of docs.
Date: Tue, 28 Jul 2009 20:03:03 +0200 [thread overview]
Message-ID: <4A6F3D57.2010602@drmicha.warpmail.net> (raw)
In-Reply-To: <4A6F29C5.6030608@gmail.com>
Saikiran Madugula venit, vidit, dixit 28.07.2009 18:39:
> OOps, forgot to cc vger.kernel.org
>
> Thomas Rast wrote:
>> NAK. Presumably you are using an asciidoc 8.x? Please check if
>> saying
>>
>> make ASCIIDOC8=Yes man
>>
>> fixes the problem. Read the comments in Documentation/Makefile for
>> advice on what precise combination of options you should use. Also,
>> if you do not want to actually work on docs
>>
>> make quick-install-man
>>
>> is a much less painful way to get manpages (in this case, from Junio's
>> 'man' branch that has preformatted manpages for 'master').
>
> My asciidoc version is 8.4.1. Yes "make ASCIIDOC8=yes" seems to have built with
> out any problems. Thanks for quick-install-man tip, I should have read till the
> end of INSTALL document :) .
>>
>> I put the +++ in there to stop the version I used at the time from
>> rendering the closing backtick as part of the URL and garbling the
>> entire paragraph in the process. To be precise, with asciidoc 8.2.7
>> and without the +++ I get
>>
>> Clone it with <tt>git clone <a href="file:///path/to/repo</tt">file:///path/to/repo</tt</a>>.
>>
>> in the HTML output. Note the nested tags. (With asciidoc 8.4.5 the
>> problem appears to be fixed.)
>>
>
> People would start using latest versions of ascii doc which has no problems,
> wouldn't it be better if the default compile options suit them ? Also, it would
> be good if "make install man", would do "quick-install-man" as default to
> prevent users from the painful compilation of manpages everytime they try to
> install latest git.
"make install" does not build any documentation at all, so that should
be no source of pain.
The user decides which we to go: install-man or quick-install-man.
Having the defaults set up so that recent "mainstream" versions of the
tool chain work without extra options may sound like a good idea - but
that would mean changing options again and again. I think we should do
this for major milestones (say git 1.7).
Michael
next prev parent reply other threads:[~2009-07-28 18:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-28 16:39 [PATCH] Documentation: Fix build failure of docs Saikiran Madugula
2009-07-28 18:03 ` Michael J Gruber [this message]
2009-07-29 9:09 ` Saikiran Madugula
-- strict thread matches above, loose matches on Subject: below --
2009-07-28 15:38 Saikiran Madugula
2009-07-28 16:02 ` Thomas Rast
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=4A6F3D57.2010602@drmicha.warpmail.net \
--to=git@drmicha$(echo .)warpmail.net \
--cc=git@vger$(echo .)kernel.org \
--cc=hummerbliss@gmail$(echo .)com \
--cc=trast@student$(echo .)ethz.ch \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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