All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Perez de Castro <aperez@igalia.com>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/wpebackend-fdo: bump to version 1.12.1
Date: Mon, 29 Aug 2022 16:47:19 +0300	[thread overview]
Message-ID: <20220829164719.GB4045490@kodama> (raw)
In-Reply-To: <20220827134525.GA37358@scaer>


[-- Attachment #1.1: Type: text/plain, Size: 826 bytes --]

Hi Yann,

On Sat, 27 Aug 2022 15:45:25 +0200 "Yann E. MORIN" <yann.morin.1998@free.fr> wrote:
 
> On 2022-08-27 15:42 +0200, Yann E. MORIN spake thusly:
> > On 2022-08-24 15:26 +0300, Adrian Perez de Castro spake thusly:
> > > This minor release fixes a crash. Release notes:
> > > 
> > >   https://wpewebkit.org/release/wpebackend-fdo-1.12.1.html
> > > 
> > > Signed-off-by: Adrian Perez de Castro <aperez@igalia.com>
> > Applied to next, thanks.
> 
> Damn, sent too fast..
> 
> I meant to ask:  the release notes state "in certain situations". Is
> that occuring often enough to warrant being applied on master?

While the crashes are not very common, it would be nice to include the
version bump in the "master" branch. I reckon the changes are rather small
and they shouldn't introduce any regression.

Cheers,
—Adrián

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 150 bytes --]

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2022-08-29 13:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-24 12:26 [Buildroot] [PATCH 1/1] package/wpebackend-fdo: bump to version 1.12.1 Adrian Perez de Castro
2022-08-27 13:42 ` Yann E. MORIN
2022-08-27 13:45   ` Yann E. MORIN
2022-08-29 13:47     ` Adrian Perez de Castro [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=20220829164719.GB4045490@kodama \
    --to=aperez@igalia.com \
    --cc=buildroot@buildroot.org \
    --cc=yann.morin.1998@free.fr \
    /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.