On Tue, Sep 29, 2015 at 01:34:03PM +0100, Stuart Henderson wrote: > On 2015/09/29 14:27, Peter Hessler wrote: > > On 2015 Sep 28 (Mon) at 22:23:49 +0200 (+0200), Matthieu Herrb wrote: > > :On Wed, Sep 16, 2015 at 02:37:38AM -0600, David Coppa wrote: > > :> > > :> Hi! > > :> > > :> Here's an update to libxcb-1.11.1 > > :> > > :> Changes: > > :> > > :> - Expose 64-bit sequence numbers for XLib > > :> - Call _xcb_wake_up_next_reader from xcb_wait_for_special_event > > :> - Fix a thread hang with xcb_wait_for_special_event() > > :> > > :> Tested in a full xenocara rebuild on amd64. > > :> I think a minor crank is required. > > : > > :The diff looks ok, but we currently don't have anything in xenocara > > :using the new functions. Do you know any application in ports that > > :would use it if available ? > > : > > > > Is it that painful to bump a library minor? I think we should always be > > safe and bump even when we don't know if it would be used. > > Oh I was assuming this related to testing rather than bumps. Yes a bump > is necessary, it's not about what current ports do, but about what future > updates might start using.
Yes I was referring to testing. Of course a minor bump is needed. In the mean time I read the code a bit more. I was wrong, the new code is used indeed by the old API too. So it is tested if you run normal X applications. so ok matthieu@. -- Matthieu Herrb
pgpIrLqDJg5eT.pgp
Description: PGP signature
