From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [pull request] Pull request for branch yem-misc-updates
Date: Mon, 01 Jul 2013 11:42:39 +0200 [thread overview]
Message-ID: <87bo6mvcog.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <cover.1372545265.git.yann.morin.1998@free.fr> (Yann E. MORIN's message of "Sun, 30 Jun 2013 00:38:11 +0200")
>>>>> "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.
Committed series, thanks.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2013-07-01 9:42 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 ` Peter Korsgaard [this message]
2013-07-01 10:03 ` [Buildroot] [pull request] Pull request for branch yem-misc-updates Arnout Vandecappelle
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=87bo6mvcog.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--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