Barton C Massey
bart at cs.pdx.edu
Mon Apr 17 09:55:42 PDT 2006
Maybe one of the things we want to do is to have the bugs
post to this list? (Is this what you were suggesting?)
It's not like it would swamp us in traffic...
I agree---we have done a mediocre job of letting ourselves
know what is going on. :-) Other suggestions for improving
communication among the group gratefully entertained.
In message <44438EBC.3030907 at brandeis.edu> you wrote:
> It might be nice if these things were put up on the list. Often times
> there seem to be changes that just come out of the blue. I'm not saying
> that the list needs to be involved in every discussion (that would
> probably slow us down a lot) but that we're at least informed of what's
> going on. It also gives us an historical archive of sorts which could
> prove useful.
> Barton C Massey wrote:
> > Other than the horrible name :-), and the lack of an obvious
> > use case for the function :-), I'm not seeing what the issue
> > is. Could you or Josh attach a summary of the
> > question/problem to bug #6120, and maybe post it here?
> > Inquiring minds want to know!
> > Thanks,
> > Bart
> > In message <20060417044541.GM6307 at id.minilop.net> you wrote:
> >>> * Set a non-zero library version. Jamey, can we officially declare the
> >>> API/ABI stable?
> >> Recently you and I got as far as deciding that XCBGetRequestRead and
> >> isn't the right function for its job, but we had a little trouble with
> >> what we should provide instead. I think we should quickly wrap up that
> >> conversation before finally doing the ABI bump. This is bug #6120, and
> >> no other bugs affect API/ABI in backwards-incompatible ways.
> > _______________________________________________
> > Xcb mailing list
> > Xcb at lists.freedesktop.org
> > http://lists.freedesktop.org/mailman/listinfo/xcb
> Xcb mailing list
> Xcb at lists.freedesktop.org
More information about the Xcb