Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Your build results for 2018-12-04
Date: Thu, 06 Dec 2018 20:16:01 +0200	[thread overview]
Message-ID: <87efaujzby.fsf@tkos.co.il> (raw)
In-Reply-To: <f3cpi33oica7lbub1hjw72x0.1544043243948@email.android.com>

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.

Hope this helps,
baruch

> -------- Original message --------
> From: Bartosz Golaszewski <brgl@bgdev.pl>
> Date: 12/5/18 2:50 PM (GMT-06:00)
> To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
> Cc: buildroot at buildroot.org
> Subject: Re: [Buildroot] [autobuild.buildroot.net] Your build results for 2018-12-04
>
> ?r., 5 gru 2018 o 08:00 Thomas Petazzoni
> <thomas.petazzoni@bootlin.com> napisa?(a):
>>
>> Hello,
>>
>> This is the list of Buildroot build failures that occured on
>> 2018-12-04, and for which you are a registered architecture developer
>> or package developer. Please help us improving the quality of
>> Buildroot by investigating those build failures and sending patches to
>> fix them. Thanks!
>>
>> Results for the 'master' branch
>> ===============================
>>
>> Build failures related to your packages:
>>
>>  powerpc64le |                pulseview-0.4.1 | http://autobuild.buildroot.net/results/9a9e8d390941cbfde70c4b4033d7e68ce28e041e
>>
>> --
>> http://autobuild.buildroot.net
>
> Pending patch[1] will fix it.
>
> Best regards,
> Bartosz Golaszewski
>
> [1] http://lists.busybox.net/pipermail/buildroot/2018-December/237718.html

--
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -

  reply	other threads:[~2018-12-06 18:16 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 [this message]
2018-12-08 12:00       ` 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=87efaujzby.fsf@tkos.co.il \
    --to=baruch@tkos.co.il \
    --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