On Wed, Nov 25, 2020 at 06:11:29PM +0000, Christoph Hellwig wrote: > On Wed, Nov 25, 2020 at 02:06:06PM -0400, Jason Gunthorpe wrote: > > It uses a empty 'cover-letter' commit and automatically transforms it > > into exactly the right stuff. Keeps track of everything you send in > > git, and there is a little tool to auto-run git range-diff to help > > build change logs.. > > > > https://github.com/jgunthorpe/Kernel-Maintainer-Tools/blob/master/gj_tools/cmd_send_patches.py > > > > I've been occasionaly wondering if I should suggest Konstantin add a > > sending side to b4, maybe using some of those ideas.. > > > > (careful if you run it, it does autosend without prompting) > > The looks pretty fancy. Here is my trivial patchbomb.sh script > > #!/bin/sh > > COVERLETTER=$1 > PATCHES=$2 > > git send-email --annotate --to-cover --cc-cover $1 $2 > > still needs the git basecommit..endcommit notation, but it fires > up the series for review. annotate is OK, I used that for a long time.. My main gripe was it didn't setup the to/cc until after the annotate editor closes. Jason _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
