Hi Michael, > On Thu, 11 Nov 2010 18:37:39 -0800, Russ Allbery wrote: > > Michael Gilbert <michael.s.gilb...@gmail.com> writes: > > > > > Would anyone be willing to sponsor another RC-fix upload? This new > > > libvdpau package fixes bug #603220: > > > http://mentors.debian.net/debian/pool/main/l/libvdpau > > > > Thank you very much for your enthusiasm for fixing bugs for the release! > > But for the future, could you please wait at least a day or so after > > filing an RC bug before requesting someone sponsor an NMU for it? Usually > > the maintainers will want to at least look at the bug first. > > Why delay? The debdiff is in the bug report, and an NMU will get > uploaded to DELAYED, so the maintainer has plenty of time to act; that > is if they are indeed going to act. If not then the NMU goes through. > I don't see the problem. >
I'm sure you are aware of [1]. The second item of "Before doing an NMU" states: "Did you give enough time to the maintainer?" Unless I got something wrong, there weren't more than a few hours between the bug report and the RFS. You'll surely understand that this wouldn't even allow people living in different time zones to _notice_ your bug report. > Personally I'd prefer to not have to context-switch back to the problem > a day later when I can deal with it all at once. > While I do understand that your time is valuable and I do as well highly appreciate your contribution, please be aware that you are playing with other people's time. You'd need someone unfamiliar with the codebase review your changes and possibly do the sponsoring thereafter. Would you instead give the maintainer at least the chance to read it (by waiting for one day) you could possible avoid this. And, seriously, it's not too hard to keep an email in the draft folder for a day or so. Sending it out shouldn't require too much of a context to restore. Thanks a lot, Michael [1] http://www.debian.org/doc/developers-reference/pkgs.html#nmu
pgpnyOeDf8J7S.pgp
Description: PGP signature
