On Wed, Mar 09, 2022 at 12:47:26PM +0530, Ani Sinha wrote: > > > On Tue, 8 Mar 2022, Michael S. Tsirkin wrote: > > > On Tue, Mar 08, 2022 at 10:23:20PM +0530, Ani Sinha wrote: > > > On Tue, Mar 8, 2022 at 10:17 PM Michael S. Tsirkin <mst@xxxxxxxxxx> wrote: > > > > > > > > On Tue, Mar 08, 2022 at 10:15:11PM +0530, Ani Sinha wrote: > > > > > > > > > > > > > > > On Tue, 8 Mar 2022, Laine Stump wrote: > > > > > > > > > > > Aha! the domain of qemu-devel@xxxxxxxxxx was incorrect in the original send > > > > > > (it was "nognu.org"), so none of this thread was making it to that list. > > > > > > > > > > > > > > > Not to give any excuses but this happened because on Qemu side I never > > > > > have to type this manually. My git config is set up so that > > > > > the cc in send-email is filled up automatically using > > > > > scripts/get_maintainer.pl. On libvirt side also the domain and mailing > > > > > list is easy to remember. Its only when I have to manually type stuff that > > > > > shit happens :-) > > > > > > > > Donnu about alpine, but with mutt you can easily set up > > > > and alias and then it expands for you. > > > > > > I use alpine to only reply/review patches. I use git send-email to > > > actually send the patch. There I am not sure the best way to avoid > > > manually typing in the mailing list address. > > > > send-email supports aliases too. > > Ah cool. I just set this up with some help from > https://felipec.wordpress.com/2009/10/25/git-send-email-tricks/ . Now I > can simply say > > $ git send-email --to=qemu-list <patch> > > without worrying about typo :-) Thanks for the pointer. > So, in context of sending patches to mailing lists, especially with libvirt and QEMU, you could utilize 'git publish'. Both QEMU and libvirt have a .gitpublish config in the repo which sets some git-send email options, especially the QEMU's one is nice listing a bunch of common profile templates as well. I'd say that if you're contributing to a project which doesn't have a .gitpublish config yet, then rather than not using 'git publish', the project should adopt the config instead :). Regards, Erik
