On Tue, Feb 22, 2011 at 4:38 PM, Amit Kucheria <amit.kuche...@linaro.org> wrote: > Hi, > > We're required to cc patc...@linaro.org for all patches that we send > upstream. bzr/launchpad users are already covered or will be shortly. > > For those using git-send-email to send patches (and you really should > be), it might make sense to use the following command so you don't > forget > > $ git config --global --add sendemail.bcc "patc...@linaro.org" > > Check $HOME/.gitconfig to make sure you see "bcc = patc...@linaro.org" > under the [sendemail] section. > WARNING - this will bcc patc...@linaro.org on all patches from that > machine sent using git-send-email. > > If you want more control, and your linaro work happens in a single git > tree, you could do the following: > > $ cd <your linaro git tree> > $ git config --add sendemail.bcc "patc...@linaro.org" > > Check <your linaro git tree>/.git/config for the bcc entry as above. > Now patches send from that tree will be bcc'ed to patches@linaro. > > /Amit > p.s. There is also a sendemail.cc instead of sendemail.bcc in case you > want to use that. >
Do we need a policy on whether or not to use Bcc here? One argument for using Bcc is that it avoids replies from subscribers to the destination mailing lists from also being CC'd to patc...@linaro.org. Can your analysis cope with patc...@linaro.org receiving a whole thread, or do we need to be careful about this? Cheers ---Dave _______________________________________________ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
