Hi Pekon, On Fri, Apr 18, 2014 at 09:15:03AM +0000, Pekon Gupta wrote: > I was just wondering if there is a script which can automatically search the > git tree and update state of patch on patchwork [1].
There is, sort of. Jeremy Kerr presented a few things at Linux Plumbers a while back, and it includes a "catchup" script: http://www.linuxplumbersconf.org/2011/ocw/system/presentations/255/original/patchwork.pdf It marks "Accepted" patches based on the hash of the diff. There are also git post-recevie hooks for updating automatically. > If not then is it possible > to update the patch status from now onwards (or may be a month back) ? > This can be added as part of git-commit script used by Maintainers. > > This would be helpful in reviewing and finding references. And would be > good for Maintainers too to keep a track of pending ones. I've looked into your suggestion. I'm beginning to integrate Patchwork into my workflow, and I'll see how it works out. I still have a few kinks to work out (e.g., how to most easily mark patches as Superseded when a new version is sent, for instance), but I have a few mutt and git hooks established which help me in some of the major points. And I may end up archiving much of the older stuff, just to start relatively fresh. Any tips for using patchwork to its fullest are welcome. I'm kind of in a trial phase right now, where I'll see how much value patchwork can add. If it really is just more work (on maintaining metadata) than it helps, then I may not stick with it. > [1] http://patchwork.ozlabs.org/project/linux-mtd/list/ Regards, Brian _______________________________________________ Patchwork mailing list [email protected] https://lists.ozlabs.org/listinfo/patchwork
