From: Michael Witten <mfwitten@gmail.com>
To: Tomas Carnecky <tom@dbservice.com>
Cc: Sultan Shakir <sshakirflhosp@gmail.com>, git@vger.kernel.org
Subject: Re: Git and Documentation
Date: Tue, 10 Aug 2010 15:56:57 -0500 [thread overview]
Message-ID: <AANLkTikK6_MqPQSg944DNfVULT3ccN9xMsObCAqHqxY_@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimK_ounhk1Qou02V_3+JjpY9Y5ZO3OO2uRn6A7k@mail.gmail.com>
On Tue, Aug 10, 2010 at 15:47, Michael Witten <mfwitten@gmail.com> wrote:
> On Tue, Aug 10, 2010 at 15:31, Tomas Carnecky <tom@dbservice.com> wrote:
>> If the documentation is generated as part of the build, then there is no
>> reason to have it part of the history - you can always rebuild it from
>> the source. For the same reason you don't put compiled source into git.
>
> Well, theoretically.
>
> According to:
>
> http://git.kernel.org/?p=git/git.git;a=blob_plain;f=MaintNotes;hb=todo
>
> the git project's repository itself tracks generated documentation for
> practical reasons:
>
> The "html" and "man" [branches] are
> autogenerated documentation from the
> tip of the "master" branch; the tip
> of "html" is extracted to be visible
> at kernel.org at:
>
> http://www.kernel.org/pub/software/scm/git/docs/
>
I should add that generating documentation is time consuming and often
requires brittle software; there's a lot to gain by having one system
produce the same output for virtually everyone else.
next prev parent reply other threads:[~2010-08-10 20:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTik_rO_+az5kE=yhfXK1uUO3v0RKdcO2hzFBcZym@mail.gmail.com>
2010-08-09 17:35 ` Git and Documentation Sultan Shakir
2010-08-09 20:43 ` Ævar Arnfjörð Bjarmason
2010-08-10 19:55 ` Sultan Shakir
2010-08-10 20:31 ` Tomas Carnecky
2010-08-10 20:47 ` Michael Witten
2010-08-10 20:56 ` Michael Witten [this message]
2010-08-11 16:34 ` Sultan Shakir
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=AANLkTikK6_MqPQSg944DNfVULT3ccN9xMsObCAqHqxY_@mail.gmail.com \
--to=mfwitten@gmail.com \
--cc=git@vger.kernel.org \
--cc=sshakirflhosp@gmail.com \
--cc=tom@dbservice.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).