Hi Guilherme,
> I'd appreciate some feedback on this; specially whether or not this is
> something that's going to be useful upstream and, if so, if the current
> approach is reasonable.
This is the approach I (and other patchwork maintainers) have been
using:
git rev-list rev1..rev2 |
while read commit
do
hash=$(git show $commit | pwparser --hash)
pwclient update -h $hash -s Accepted -c $commit
done
(`pwparser` being apps/patchwork/parser.py)
If you'd like to make this more automated, I'd much rather something
that doesn't require a full patchwork source tree to work, and can be
easily run on maintainers' machines. It's very unlikely that we'd run
these processes on ozlabs.org or kernel.org, due to the high processing
overhead.
Cheers,
Jeremy
_______________________________________________
Patchwork mailing list
[email protected]
https://lists.ozlabs.org/listinfo/patchwork
