From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] cups: deprecate package due to security issues
Date: Mon, 16 Mar 2015 22:26:58 +0100 [thread overview]
Message-ID: <20150316222658.607f3105@free-electrons.com> (raw)
In-Reply-To: <1425649164-31813-1-git-send-email-gustavo@zacarias.com.ar>
Dear Gustavo Zacarias,
On Fri, 6 Mar 2015 10:39:24 -0300, Gustavo Zacarias wrote:
> Also mark packages that depend on cups as deprecated as well for easier
> tracking.
>
> It would probably be better to mark it as a legacy option so users get a
> warning when migrating configuration files, but it would require a
> direct removal for that.
>
> Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
Applied, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-03-16 21:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-06 13:39 [Buildroot] [PATCH] cups: deprecate package due to security issues Gustavo Zacarias
2015-03-06 14:09 ` Thomas Petazzoni
2015-03-06 14:30 ` Gustavo Zacarias
2015-03-07 0:37 ` [Buildroot] Adding deprecated packages to legacy [was: cups: deprecate package due to security issues] Arnout Vandecappelle
2015-03-16 21:26 ` Thomas Petazzoni [this message]
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=20150316222658.607f3105@free-electrons.com \
--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