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 09:25:40 +0100 [thread overview]
Message-ID: <20130320092540.4b14570b@skate> (raw)
In-Reply-To: <CAHXCMMJenyhQiKPp+vKbcM_c280ghGVeAG9tsGxtXnR0s3b0CA@mail.gmail.com>
Dear Samuel Martin,
On Tue, 19 Mar 2013 22:52:11 +0100, Samuel Martin wrote:
> > I'm not sure to understand the problem with the dates. I'd say you
> > shouldn't put the date specifically in the list of packages. I would
> > expect "make manual-pdf" to generate the list of packages with your
> > script, get it included into the manual sources, and get the manual
> > built.
> >
> > Separately, we may want to introduce something at the beginning of the
> > manual that says at which date the manual was built, and on which Git
> > version of the Buildroot sources. But I don't see a reason to make this
> > related to the list of packages specifically.
> Just to be sure, here, you mean something like a non-versioned version.txt file,
> which would be automatically generated and included in manual.txt?
Yes, something like that.
Best regards,
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 8:25 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 [this message]
2013-03-20 12:58 ` Lionel Orry
2013-03-20 13:49 ` Thomas Petazzoni
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=20130320092540.4b14570b@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.