# cover letter and cc list 4 messages from 2015-03-20 to 2016-02-26. Participants: Olaf Hering, Junio C Hamano, Vineet Gupta. Thread: https://gitlist.dev/t/38869 ## Olaf Hering, 2015-03-20 17:35 Subject: cover letter and cc list Message-ID: <20150320173504.GA6162@aepfle.de> URL: https://gitlist.dev/e/20150320173504.GA6162%40aepfle.de ``` What does it take to send the cover letter to all people which are listed in the Cc: list of the following patches? Each patch has a different Cc: list. The "git send-email --help" command suggests that this cmdline should do it. But the cover letter goes just to the address listed in --to=: env TMPDIR=/dev/shm LC_ALL=C git send-email -M --stat --annotate \ --cover-letter --cc-cover --to=$address \ $base..$head Thanks, Olaf ``` ## Junio C Hamano, 2015-03-20 18:08 Subject: Re: cover letter and cc list Message-ID: URL: https://gitlist.dev/e/xmqqpp83ee2z.fsf%40gitster.dls.corp.google.com In-Reply-To: <20150320173504.GA6162@aepfle.de> ``` Olaf Hering writes: > What does it take to send the cover letter to all people which are > listed in the Cc: list of the following patches? Each patch has a > different Cc: list. The "git send-email --help" command suggests that > this cmdline should do it. But the cover letter goes just to the address > listed in --to=: > > env TMPDIR=/dev/shm LC_ALL=C git send-email -M --stat --annotate \ > --cover-letter --cc-cover --to=$address \ > $base..$head First step is not to drive format-patch from within send-email I would think. Instead prepare them in files in a directory (with format-patch -o $dir). You can edit Cc: header in 0000-*.patch message while you proof-read what you are going to send out. ``` ## Olaf Hering, 2015-03-23 08:18 Subject: Re: cover letter and cc list Message-ID: <20150323081840.GB9332@aepfle.de> URL: https://gitlist.dev/e/20150323081840.GB9332%40aepfle.de In-Reply-To: ``` On Fri, Mar 20, Junio C Hamano wrote: > Olaf Hering writes: > > > What does it take to send the cover letter to all people which are > > listed in the Cc: list of the following patches? Each patch has a > > different Cc: list. The "git send-email --help" command suggests that > > this cmdline should do it. But the cover letter goes just to the address > > listed in --to=: > > > > env TMPDIR=/dev/shm LC_ALL=C git send-email -M --stat --annotate \ > > --cover-letter --cc-cover --to=$address \ > > $base..$head > > First step is not to drive format-patch from within send-email I > would think. Instead prepare them in files in a directory (with > format-patch -o $dir). You can edit Cc: header in 0000-*.patch > message while you proof-read what you are going to send out. Thanks. Then I misinterpreted what --cc-cover actually means. All Cc: lines have to be present in the cover letter already. Would be nice if git would run a command like this to put the list into the coverletter: # git log --format=%b $base..$head | grep -iw ^cc: | sort -u In the meantime I will remember to do that step manually. Olaf ``` ## Vineet Gupta, 2016-02-26 12:35 Subject: Re: cover letter and cc list Message-ID: <56D04683.3080201@synopsys.com> URL: https://gitlist.dev/e/56D04683.3080201%40synopsys.com In-Reply-To: <20150323081840.GB9332@aepfle.de> ``` -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On Monday 23 March 2015 01:48 PM, Olaf Hering wrote: > On Fri, Mar 20, Junio C Hamano wrote: > >>> Olaf Hering writes: >>> >>>>> What does it take to send the cover letter to all people which are >>>>> listed in the Cc: list of the following patches? Each patch has a >>>>> different Cc: list. The "git send-email --help" command suggests >>>>> that this cmdline should do it. But the cover letter goes just to the >>>>> address listed in --to=: >>>>> >>>>> env TMPDIR=/dev/shm LC_ALL=C git send-email -M --stat --annotate \ >>>>> --cover-letter --cc-cover --to=$address \ $base..$head >>> >>> First step is not to drive format-patch from within send-email I would >>> think. Instead prepare them in files in a directory (with format-patch >>> -o $dir). You can edit Cc: header in 0000-*.patch message while you >>> proof-read what you are going to send out. > Thanks. Then I misinterpreted what --cc-cover actually means. All Cc: lines > have to be present in the cover letter already. Would be nice if git would > run a command like this to put the list into the coverletter: > > # git log --format=%b $base..$head | grep -iw ^cc: | sort -u > > In the meantime I will remember to do that step manually. > > Olaf I have the exact same requirement, to create a union of CC in patches for cover-letter. That way sending a series to different people gives them the right context with cover-letter and individual patch. Now man git send-email mentions --[no-]cc-cover. I quote "emails found in Cc: headers in the first patch of the series (typically the cover letter) are added to the cc list for each email set..." I certainly want the reverse, but the question is how does one get about getting an address in cover letter in first place. Thx, - -Vineet -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJW0EaDAAoJEGnX8d3iisJevuMQALMNQv7IiOTc78A0GMDZpBx4 cAEY2mPu29uJG0rRq8vaWxwBEAAoIflqUEiv9ygHwtvI1YDBGgt3RsEuqTMdj1eI JboZy4cpn04XVKRtcEU1iXf8Qp5uGmOgBUSwP5VaawTpGxIn43KJjyFwvq7h9Sps lsuOtY5rO1xq1B4ktmolF93unwI5R68moNTHhpOilOcBwbNVApouMnJ0c64ritPw hn9pUWST+rtL9pbqUas4PRxHL4vUAhIQkswlxxZvaVhlC9WK6AY2nMTWmz0Pcmlc WbGD1nulGJMXkHR4G02GhSbO2zsy8o5vJii2inFCwl7eWC5LIdfc8w+ssDYJ9Zlz beXuRxYy5zgQQzCpd9d1o7ZMjbSEuWizgPJ9a+lGPfqeqB/cp9emdbOUOc7CMhXn 5C3nDtOIgkchnZw3otgbUmGQCbiIHTN4tMQHbXrp0suu2mPCkYA9H8SqBRANPy1k AfU1FCvgQBjGgezV4IOBLrqi3vqoacQqriYIyYmUq0rnuwI6fT09OwfvAa2uVugT BWuuzpW1gBiiSKfYstC+ZzoZCnD8Ia5HsaKNtFxfxia2ekFC50RTkSR3ScSVnlKI 77uLzflHsoZvFrla1mgLn+D4pn3yzSUdcd9lFIBAkBqgR1T5mKjT3HaSDOdMDJRz KiRJrh3G8ZC7hYeAj3Kx =GzhS -----END PGP SIGNATURE----- ```