From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/5] manual: add a make target 'manual-update-lists'
Date: Wed, 20 Mar 2013 14:49:24 +0100 [thread overview]
Message-ID: <20130320144924.53b66373@skate> (raw)
In-Reply-To: <CAKAx1cicUqrkg1Q1VHZQAzPc7YivcfiJdEZoJ9DbErazMiN2CQ@mail.gmail.com>
Dear Lionel Orry,
On Wed, 20 Mar 2013 13:58:26 +0100, Lionel Orry wrote:
> Can I suggest something like adding this line at the beginning of the manual:
>
> Manual generated from git revision {sys:git rev-parse HEAD} on
> {docdate} {doctime}.
>
> This avoids an extra file generation, asciidoc can do it by itself.
Sounds even better! Thanks for the suggestion.
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:[~2013-03-20 13:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-12 4:47 [Buildroot] [pull request v4] Pull request for branch for-master/doc Samuel Martin
2013-03-12 4:47 ` [Buildroot] [PATCH 1/5] support/scripts: add gen-manual-lists.py Samuel Martin
2013-03-12 4:47 ` [Buildroot] [PATCH 2/5] manual: add a make target 'manual-update-lists' Samuel Martin
2013-03-12 7:59 ` Thomas Petazzoni
2013-03-12 8:41 ` Samuel Martin
2013-03-13 7:39 ` Thomas Petazzoni
2013-03-19 21:52 ` Samuel Martin
2013-03-20 8:25 ` Thomas Petazzoni
2013-03-20 12:58 ` Lionel Orry
2013-03-20 13:49 ` Thomas Petazzoni [this message]
2013-03-12 22:04 ` Arnout Vandecappelle
2013-03-12 4:47 ` [Buildroot] [PATCH 3/5] manual: cleanup appendix.txt Samuel Martin
2013-03-12 4:47 ` [Buildroot] [PATCH 4/5] Makefile: add to the release target a warning about the manual updates Samuel Martin
2013-03-12 4:47 ` [Buildroot] [PATCH 5/5] manual: update generated lists Samuel Martin
2013-03-13 19:48 ` [Buildroot] [pull request v4] Pull request for branch for-master/doc Arnout Vandecappelle
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=20130320144924.53b66373@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