From: Tomas Carnecky <tom@dbservice.com>
To: Sultan Shakir <sshakirflhosp@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Git and Documentation
Date: Tue, 10 Aug 2010 22:31:51 +0200 [thread overview]
Message-ID: <4C61B737.50108@dbservice.com> (raw)
In-Reply-To: <AANLkTikwVfymGB8oEQUN=1LMWoif22p316mm=PzSxQwa@mail.gmail.com>
On 8/10/10 9:55 PM, Sultan Shakir wrote:
> Yes I guess I could. I am a little new at this. I got the same idea
> after watching Stephen Wood's video here:
> http://developer.yahoo.com/yui/theater/video.php?v=woods-yuiconf2009-yuidoc
> . He had 3 rules/guidelines that might work if we use YUI Doc to
> generate the documentation:
>
> 1) Generate documentation as part of the build
> 2) Don’t manually check documentation in to VCS (do it automatically)
> 3) Treat documentation comments like code
>
> I am not sure how to make it run as part of my build process though.
Please don't top post.
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.
And how to generate the doc as part of the build? That's up to you and
very much depends on what build system you use.
tom
next prev parent reply other threads:[~2010-08-10 20:32 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 [this message]
2010-08-10 20:47 ` Michael Witten
2010-08-10 20:56 ` Michael Witten
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=4C61B737.50108@dbservice.com \
--to=tom@dbservice.com \
--cc=git@vger.kernel.org \
--cc=sshakirflhosp@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).