From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC] Using AsciiDoc for the Buildroot manual
Date: Tue, 9 Aug 2011 17:02:09 +0200 [thread overview]
Message-ID: <20110809170209.6cb31763@skate> (raw)
In-Reply-To: <8739hblq7q.fsf@macbook.be.48ers.dk>
Le Mon, 08 Aug 2011 20:20:57 +0200,
Peter Korsgaard <jacmet@sunsite.dk> a ?crit :
> Thomas, have you done any changes since you posted the patches? If so,
> please repost.
No, I haven't done any changes since I posted the patches.
N.B: I am on holidays, with an intermittent access to an Internet
connection.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2011-08-09 15:02 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
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 [this message]
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=20110809170209.6cb31763@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox