[prev in list] [next in list] [prev in thread] [next in thread] 

List:       git
Subject:    Re: [ANNOUNCE] GIT preformatted documentation available.
From:       Adrien Beau <adrienbeau () gmail ! com>
Date:       2005-12-28 16:51:37
Message-ID: 94fc236b0512280851n797ecbedjecae3f8131b84369 () mail ! gmail ! com
[Download RAW message or body]

On 12/27/05, Junio C Hamano <junkio@cox.net> wrote:
>
> I was asked to provide pre-formatted man pages (and perhaps html
> pages), since the time of kernel developers are better spent on
> what they do best, rather than preparing the xmlto toolchain.
>
> I was planning to do a tarball every time I do a "release", but
> that would mean it is no better than the current way --- you
> could extract manpages out of rpm anyway.
>
> So instead, I'll do independent branches "html" and "man" in
> git.git repository to keep the preformatted documentation.

Having preformatted documentation is a great step forward, but it
would be even better if we could have it without installing some weird
RPM tool or a local copy of the Git repository -- not all my machines
have that.

Besides, it's not very beginner- or newcomer-friendly. Grab the
source; discover you need a complex toolchain to have manpages; maybe
learn sometime later that "all you had to do" was get an RPM and
explode some parts of it -- nah, it just doesn't feel right.

You're already generating five RPMs and two tarballs everytime you
release a version, would it be much more taxing to generate a third
tarball?

That said, those two new branches are neat. Thanks!
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
[prev in list] [next in list] [prev in thread] [next in thread]