From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Your build results for 2018-12-04
Date: Sat, 08 Dec 2018 13:00:50 +0100 [thread overview]
Message-ID: <875zw45itp.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <87efaujzby.fsf@tkos.co.il> (Baruch Siach's message of "Thu, 06 Dec 2018 20:16:01 +0200")
>>>>> "Baruch" == Baruch Siach <baruch@tkos.co.il> writes:
> Hi David,
> David J. Fogle writes:
>> Is this patch going to be put into 2018.11, or is this going into
>> 2019.02. I am rather new to your project, forgive me not knowing how
>> your patch cycle works.
> This patch fixes an issue in the current master branch. So this patch
> (or a better one) will be applied to that branch. The master branch will
> be released as 2019.02.
> Patches fixing issues that affect stable branches (currently 2018.08.x
> and 2018.02.x are maintained) will be backported to these branches. In
> the case of this patch, stable branches seem not to be affected. The
> build failure trigger is the bump of pulseview to version 0.4.1. This
> bump is not in the stable branches.
Correct. Notice that I will create a 2018.11.x branch this weekend and
start maintaining that instead of 2018.08.x.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2018-12-08 12:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20181205070024.027E420A59@mail.bootlin.com>
2018-12-05 20:51 ` [Buildroot] [autobuild.buildroot.net] Your build results for 2018-12-04 Bartosz Golaszewski
2018-12-05 20:52 ` David J. Fogle
2018-12-06 18:16 ` Baruch Siach
2018-12-08 12:00 ` 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=875zw45itp.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