From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC] Using AsciiDoc for the Buildroot manual
Date: Fri, 5 Aug 2011 10:22:51 +0200 [thread overview]
Message-ID: <20110805102251.7a293244@skate> (raw)
In-Reply-To: <87ipqcmhf7.fsf@macbook.be.48ers.dk>
Le Fri, 05 Aug 2011 09:44:12 +0200,
Peter Korsgaard <jacmet@uclibc.org> a ?crit :
> Thomas> For the first part, I guess the "make release" target can be
> Thomas> extended to generate the documentation and then include it into
> Thomas> the tarball, but I think this is something to be discussed with
> Thomas> Peter.
>
> Indeed. For releases I think atleast the text and single-html version
> should get included in the tarball.
So, should we extend the release to target to uncompress the tarball
after it has been generated by git archive, generate the documentation,
add it to the release directory, and re-create the tarball? Or is
there a better way?
> We also need to setup something with
> a git hook to regenerate (some of) the documentation on the server
> whenever any of the source files changes. Currently the website is
> simply a git checkout managed from cron on the server, and there's no
> asciidoc on the server, but presumably that's just a question about
> asking the osuosl.org guys for it.
In order to move forward on this, can we start discussing this with the
osuosl.org people?
> Well, so far I've only heard positive feedback, so I would say: Go for
> it!
Great!
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2011-08-05 8:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-04 21:23 [Buildroot] [RFC] Using AsciiDoc for the Buildroot manual Thomas Petazzoni
2011-08-04 21:23 ` [Buildroot] [PATCH 1/5] manual: convert existing documentation to the asciidoc format Thomas Petazzoni
2011-08-04 21:23 ` [Buildroot] [PATCH 2/5] manual: provide make targets to build the documentation Thomas Petazzoni
2011-08-04 23:05 ` Yann E. MORIN
2011-08-04 21:23 ` [Buildroot] [PATCH 3/5] remove the old buildroot.html documentation Thomas Petazzoni
2011-08-04 21:23 ` [Buildroot] [PATCH 4/5] remove Glibc_vs_uClibc document Thomas Petazzoni
2011-08-04 21:23 ` [Buildroot] [PATCH 5/5] manual: ignore generated files Thomas Petazzoni
2011-08-04 22:56 ` [Buildroot] [RFC] Using AsciiDoc for the Buildroot manual Grant Edwards
2011-08-05 5:42 ` Thomas De Schampheleire
2011-08-05 6:39 ` Thomas Petazzoni
2011-08-05 7:44 ` Peter Korsgaard
2011-08-05 8:22 ` Thomas Petazzoni [this message]
2011-08-07 19:18 ` Peter Korsgaard
2011-08-07 19:24 ` Yann E. MORIN
2011-08-08 18:20 ` Peter Korsgaard
2011-08-09 15:02 ` Thomas Petazzoni
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=20110805102251.7a293244@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.