spice refactoring: workflow suggestion

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

 



Hi,

As in a mailing list it is a bit hard to track of the status of each
PATCH (acked/reviewed/pushed) and we still have tons of batch of
patches to apply/test/review I would like to suggest the following:

1-) When a batch is pushed, send an email in-reply-to 00/00 mail saying
that patches were pushed.
-- This really helps when one is behind following the changes

2-) Push series as a whole when acked instead of pushing each patch
when acked. In case a few patches of a series are taking time but a
few have been acked, maybe pushing those acked but let us know with
an email
-- Reviewing a patch to later on see that it was pushed already means
time lost. I believe an email is quicker then matching which patch awas
pushed or not.

3-) Might sound silly but as this involves lots of patchs in a short
period, it might be interesting to have acked-by, tested-by, reviewed-by
? At least for the refactoring...

Any thoughts?
Regards,
  Victor Toso
_______________________________________________
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]