Re: To warn or not to warn

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> That said, you both agree about keeping that warning and going out of our
> way to please xorg, so I'm fine with any patches you agree on ;)

Sure; two of us agree.  However, Søren has raised concerns, and has not yet
further commented.  And Søren clearly deserves a substantial voice in
what happens to this code.

But I feel that I have asked politely, and have waited a polite amount of time,
so it's reasonable for me to agitate for resolution.

I get the sense that this happens with this project, and with Søren in
particular; he seems to be particularly slammed for time, and that there
seems to be a 'oh well, we waited long enough, let's just commit it anyway'
attitude.

I do have commit access, so I can just commit.  But I'd appreciate
some explicit guidance - is there some time period that is agreed to
be reasonable to wait for further response?  Have I met that yet?
(I've mentally assigned '1 month' as being said reasonable window,
and it's been a month since I first raised this issue).

Do we just prefer to go ahead and commit and revert if and
when we later disagree?  That approach seems like a recipe
for disaster to me...

Cheers,

Jeremy
_______________________________________________
Spice-devel mailing list
Spice-devel@xxxxxxxxxxxxxxxxxxxxx
http://lists.freedesktop.org/mailman/listinfo/spice-devel



[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]     [Monitors]