From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libostree: bump to version 2018.2
Date: Sun, 18 Feb 2018 21:58:55 +0100 [thread overview]
Message-ID: <87wozaj9ps.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20180217110401.GC20477@gmail.com> (Marcus Folkesson's message of "Sat, 17 Feb 2018 12:04:01 +0100")
>>>>> "Marcus" == Marcus Folkesson <marcus.folkesson@gmail.com> writes:
> Hello Peter,
> On Thu, Feb 15, 2018 at 10:17:10PM +0100, Peter Korsgaard wrote:
>> >>>>> "Marcus" == Marcus Folkesson <marcus.folkesson@gmail.com> writes:
>>
>> > Signed-off-by: Marcus Folkesson <marcus.folkesson@gmail.com>
>>
>> Does this need to go to master for the 2018.02 release? According to the
>> release notes it seems to be a mix of bugfixes and new features.
> I'm not sure what qualifies a bump to go to master, but sure, it does
> not hurt.
master material during the stabilization phase is stuff fixing
security/important issues, preferably without adding any new features.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2018-02-18 20:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-15 20:44 [Buildroot] [PATCH] libostree: bump to version 2018.2 Marcus Folkesson
2018-02-15 21:17 ` Peter Korsgaard
2018-02-17 11:04 ` Marcus Folkesson
2018-02-18 20:58 ` Peter Korsgaard [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=87wozaj9ps.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox