On Mon, Dec 08, 2014 at 01:53:43PM +0100, Marc-André Lureau wrote: > This contradicts a bit the fact that you can do commit without review. > > I said "quickly", doing thorough review of all commits before a > release is not doable. But it is the role of the maintainer to check > all the commits that go in a repository, because we don't have ways to > enforce that all patches are the one that are ack on ML. (and I don't > think we need that, to me the process works well so far) If you send all patches to spice-devel either for ACKing, or as a notice that you pushed a patch as trivial, then this kind of commits can be caught through spice-commits@ Then maybe the person doing the release won't trust people with commit access to commit the patches that were ACKed unmodified, which is another can of worms ;) Christophe
Attachment:
pgpmvrPmJo6gT.pgp
Description: PGP signature
_______________________________________________ Spice-devel mailing list Spice-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/spice-devel