All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] manual: autogenerate *-list.txt
Date: Sun, 25 Nov 2012 23:31:24 +0100	[thread overview]
Message-ID: <50B29C3C.5090702@mind.be> (raw)
In-Reply-To: <1353544211-9308-2-git-send-email-s.martin49@gmail.com>

On 22/11/12 01:30, Samuel Martin wrote:
> I wonder whether the deprecated-list.txt file should be kept under
> scm; here I've just removed it and auto-generate it whenever the
> manual is built.
>
> It works well because the python script does not miss anything... so far.
>
> However, at the end, manual checking is still recommended.
>
> OTOH, keeping the deprecated-list.txt file under scm allows us to
> enforce synchronization between marking something as deprecated and
> the update of this list.

  I think these things should be kept under SCM.  Not just because manual
checking is recommended, but also because I don't like writing anything outside
the output directory.  Some people may have the buildroot tree in a shared,
readonly location.

  Regards,
  Arnout

-- 
Arnout Vandecappelle                               arnout at mind be
Senior Embedded Software Architect                 +32-16-286540
Essensium/Mind                                     http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium                BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2012-11-25 22:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-22  0:30 [Buildroot] [PATCH 1/2] manual: add support to autogenerate *-list.txt Samuel Martin
2012-11-22  0:30 ` [Buildroot] [PATCH 2/2] manual: " Samuel Martin
2012-11-25 22:31   ` Arnout Vandecappelle [this message]
2012-11-26  5:15     ` Samuel Martin
2012-11-28 21:46       ` Samuel Martin
2012-11-28 21:43 ` [Buildroot] [PATCH 1/2] manual: add support to " Samuel Martin

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=50B29C3C.5090702@mind.be \
    --to=arnout@mind.be \
    --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.