Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [pull request] Pull request for branch yem-misc-updates
Date: Mon, 01 Jul 2013 12:03:55 +0200	[thread overview]
Message-ID: <51D1540B.7000006@mind.be> (raw)
In-Reply-To: <87bo6mvcog.fsf@dell.be.48ers.dk>

On 07/01/13 11:42, Peter Korsgaard wrote:
>>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
>
>   Yann> From: "Yann E. MORIN" <yann.morin.1998@free.fr>
>   Yann> Hello All!
>
>   Yann> This two-patch series adds some cosmetics to the legacy menu.
>
>   Yann> The first patch displays the removal date in the menuconfig, to show
>   Yann> the user how old the legacy options he's using are.
>
>   Yann> The second patch adds to the top-level comment, that legacy options
>   Yann> will be removed at some point in the future, and that non-updated
>   Yann> .config files may fail to build, or run, in unpredictable ways.
>
>   Yann> If we do not intend to remove legacy options, let's just drop patch #2,
>   Yann> of course.
>
> I think we do, question is how soon? 6 months, 1 year?
>
> They are not very expensive, so I suggest we keep them for 1 year.

  I would keep them much longer, at least three years. Most distros have 
a 3 year or more 'stable' branch, so anything inexpensive that we can do 
to approximate that is good I think.


  Regards,
  Arnout
-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
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:[~2013-07-01 10:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-29 22:38 [Buildroot] [pull request] Pull request for branch yem-misc-updates Yann E. MORIN
2013-06-29 22:38 ` [Buildroot] [PATCH 1/2] legacy: print removal date in menuconfig Yann E. MORIN
2013-07-01  7:09   ` Arnout Vandecappelle
2013-06-29 22:38 ` [Buildroot] [PATCH 2/2] legacy: make it clear legacy options will be removed at some point Yann E. MORIN
2013-07-01  9:42 ` [Buildroot] [pull request] Pull request for branch yem-misc-updates Peter Korsgaard
2013-07-01 10:03   ` Arnout Vandecappelle [this message]
2013-07-01 10:09     ` Peter Korsgaard
  -- strict thread matches above, loose matches on Subject: below --
2013-07-18 21:24 Yann E. MORIN
2013-07-07 13:13 Yann E. MORIN
2013-07-07 19:39 ` Peter Korsgaard
2013-06-23 20:40 Yann E. MORIN
2013-06-03 20:15 Yann E. MORIN

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=51D1540B.7000006@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox