On Mon, Mar 06, 2017 at 11:50:06AM +0800, Christopher Li wrote: > On Mon, Mar 6, 2017 at 10:44 AM, Luc Van Oostenryck > <luc.vanoostenryck@xxxxxxxxx> wrote: > > Yes, those in the serie are the last version. > > The other ones can be discarded (I keep uptodate the status of my > > patches on patchwork). > > So far I have been using patchworks as way to fetch patches. > I should learn to use the status field. That is good to know. I keep things simple and normaly just set the status to: - 'Awaiting upstream' when you have pushed the patch on sparse-next, - 'Superseded' when I post a newer version And at more irregular interval I archive entries that are pushed to the master branch. For the CSE patch of last week, I've set its status to 'Under review' instead of 'RFC' so that is stay visible on the web page: https://patchwork.kernel.org/project/linux-sparse/list/ Note: if you use the pwclient, you can script the status update which is nice because otherwise it's a PITA to do this via the web page when you have to do more than a few. -- Luc -- To unsubscribe from this list: send the line "unsubscribe linux-sparse" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
