[PATCH] dri2: Send out event when auxillary buffers are invalidated

Tiago Vignatti tiago.vignatti at nokia.com
Fri May 14 08:30:01 PDT 2010


Hi,

On Fri, May 14, 2010 at 02:59:16PM +0200, ext Dan Nicholson wrote:
> 2010/5/14 Michel Dänzer <michel at daenzer.net>:
> > On Don, 2010-05-13 at 07:23 -0400, Kristian Høgsberg wrote:
> >>
> >> It would be nice if you could reply to a patch early on with what the
> >> status is, like "need more reviews", "looks good, will apply next time
> >> I do patches" or such.  Right now I don't know if a patch got lost, if
> >> you're not happy with it or just waiting for reviews.  If you want to
> >> be "Linus of the X server", I think you need to spend more time doing
> >> patches than you're doing now.  As it is, I'm not exactly encouraged
> >> to work on the X server.

I had the same feeling recently when for almost each patch series that I
worked I had to re-call attention by ping for comments on IRC, send again the
patch or poke explicitly someone for review. Just one-line feedback would be
much appreciated from you, Keith.

 
> Maybe there should just be multiple people who can push in to master.
> Not quite subsystem maintainers like the kernel, but just multiple
> maintainers. It wouldn't bother me if getting patches in meant getting
> them pulled by Keith, Peter or Ajax (for example). You'd still have
> the most important effect, which is experienced people being the final
> gatekeeper. I doubt there would be conflicts with minor "i'm pulling
> this" messages on mail or irc.

I agree. That might work cause will decrease a bit the burden from Keith.


My experience so far with the current development process is that we're now
employing a very nice quality on the code by doing strict review but on the
other hand it slows a bit changes on the code [0]. Both very typical features
of opensource sw, so I can live with it yeah.


Cheers,

[0] and the current code base as being cross-platform, multiple DDXes, it
sometimes slows a lot the development process, which for me is the reason of X
being considered as a pile of junk old code from outsiders.

        Tiago


More information about the xorg-devel mailing list