From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Petazzoni Date: Wed, 16 Aug 2017 16:44:53 +0200 Subject: [Buildroot] [PATCH 1/1] libepoxy: bump to version 1.4.3 In-Reply-To: <20170816164936.GD2311@momiji.helsinki.igalia.com> References: <20170814172320.16984-1-aperez@igalia.com> <20170814213113.6187b327@windsurf> <20170814230653.GB14043@momiji> <20170814221542.77518b99@windsurf> <20170816164936.GD2311@momiji.helsinki.igalia.com> Message-ID: <20170816164453.48adc3f8@windsurf> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net 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