From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH/next 1/1] package/ffmpeg: bump version to 3.4.2
Date: Thu, 15 Feb 2018 22:09:23 +0100 [thread overview]
Message-ID: <87h8qim03g.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <q3vglex27m.ln2@ID-313208.user.individual.net> (Bernd Kuhls's message of "Thu, 15 Feb 2018 19:11:38 +0100")
>>>>> "Bernd" == Bernd Kuhls <bernd.kuhls@t-online.de> writes:
> Am Thu, 15 Feb 2018 12:00:28 +0100 schrieb Peter Korsgaard:
>> > -FFMPEG_VERSION = 3.4.1 +FFMPEG_VERSION = 3.4.2
>>
>> Is this not 'master' material? Doesn't this only contain bugfixes
>> relative to 3.4.1?
> Hi Peter,
> according to the changelog http://git.videolan.org/?
> p=ffmpeg.git;a=blob;f=Changelog;h=5db7b0a8a7643bc0a9a310fc642c84e003300a8a;hb=refs/
> heads/release/3.4 it looks like the release only contains bugfixes, but
> afaics, nothing security related.
> Whether this patch should be committed to master or next branch when we
> are in -rc phase is a question I am unable to answer, I thought that only
> security bumps to the master branch are allowed during the rc phase. Did
> this change?
Well, the idea is to not add any new features after RC1, but
(security-)bugfixes are fine, so I believe this is OK for master as
well, especially as we are quite early in the RC phase.
I'll cherry pick it to master, thanks.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2018-02-15 21:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-12 16:51 [Buildroot] [PATCH/next 1/1] package/ffmpeg: bump version to 3.4.2 Bernd Kuhls
2018-02-14 20:43 ` Thomas Petazzoni
2018-02-15 11:00 ` Peter Korsgaard
2018-02-15 18:11 ` Bernd Kuhls
2018-02-15 21:09 ` Peter Korsgaard [this message]
2018-03-02 11:41 ` Romain Naour
2018-03-02 19:18 ` Bernd Kuhls
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=87h8qim03g.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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 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.