Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] libepoxy: bump to version 1.4.3
Date: Wed, 16 Aug 2017 16:44:53 +0200	[thread overview]
Message-ID: <20170816164453.48adc3f8@windsurf> (raw)
In-Reply-To: <20170816164936.GD2311@momiji.helsinki.igalia.com>

Hello,

On Wed, 16 Aug 2017 16:49:36 +0300, Adrian Perez de Castro wrote:

> > > > Since we're post -rc2 comes the question: do we want to apply this in
> > > > master (i.e to be part of the 2017.08 release) or in next.
> > > >
> > > > If it fixes a crash, we probably want it in master. But version bumps
> > > > are a bit frowned upon. How much differences are there between 1.4.1
> > > > and 1.4.3 ? Are they significant ? If they are significant, is it
> > > > possible to backport just the one patch that fixes the crash ?    
> > > 
> > > Good point. I would apply the patch as-is onto ?next?, and for the 2017.08
> > > branch it looks doable to pick just the patch that fixes the segfaults [1].
> > > I'll try and submit a patch which does just the latter.  
> > 
> > Sounds good. Thanks!  
> 
> Should I re-submit this patch with ?[PATCH/next]? in the title, or it can just
> be waiting in Patchwork as-is? I'll be glad to update it if needed.

It's OK as-is, the discussion we had, which is attached to the patch in
patchwork, makes it clear the patch is targeted for next.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2017-08-16 14:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-14 17:23 [Buildroot] [PATCH 1/1] libepoxy: bump to version 1.4.3 Adrian Perez de Castro
2017-08-14 19:31 ` Thomas Petazzoni
2017-08-14 20:06   ` Adrian Perez de Castro
2017-08-14 20:15     ` Thomas Petazzoni
2017-08-16 13:49       ` Adrian Perez de Castro
2017-08-16 14:44         ` Thomas Petazzoni [this message]
2017-08-21 21:36 ` Thomas Petazzoni

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=20170816164453.48adc3f8@windsurf \
    --to=thomas.petazzoni@free-electrons.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