Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] irssi: security bump to version 1.0.2
Date: Tue, 14 Mar 2017 22:33:02 +0100	[thread overview]
Message-ID: <20170314223302.5630350f@free-electrons.com> (raw)
In-Reply-To: <871stzv9jf.fsf@dell.be.48ers.dk>

Hello,

On Tue, 14 Mar 2017 22:21:56 +0100, Peter Korsgaard wrote:

> Well, it is both. 1.0.2 is a security fix for 1.0.1, but as we hadn't
> moved to the 1.0.x series yet it isn't a pure security bump.

It isn't at all :)

> I saw the alert so I started working on the update, and only at the end
> noticed that the issue didn't actually affect the 0.8.x series. I could
> have structured it as 2 separate patches, a bump from 0.8.21 -> 1.0.1 +
> a security bump to 1.0.2, but that seemed a bit silly to me.

Agreed, 2 patches seem silly.

> I can reword the commit text if you have a good idea about how to
> explain it?

I would simply not indicate in the title that it is a security bump. If
it were a security bump, we would have to apply it to the LTS branch,
while considering what you explained, we do not need to apply this
patch to the LTS branch, because the old 0.8.21 is unaffected. Unless
of course, 0.8.21 is affected by other security issues.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2017-03-14 21:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-14 15:00 [Buildroot] [PATCH] irssi: security bump to version 1.0.2 Peter Korsgaard
2017-03-14 21:01 ` Thomas Petazzoni
2017-03-14 21:21   ` Peter Korsgaard
2017-03-14 21:33     ` Thomas Petazzoni [this message]
2017-03-15 10:52       ` Peter Korsgaard

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=20170314223302.5630350f@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