On 27 March 2013 16:02, Sekhar Nori <nsek...@ti.com> wrote:
> Too bad. But something needs to be done about it since we all like to
> apply patches received in email ;). I have seen reports of people
> configuring gmail to know their @company.com address as another e-mail
> address they own and then using gmail SMTP to send patches (git config).
> You should try that.

I don't use ARM's email id for sending mails and linaro id uses gmail servers
only for sending mails..

The problem is, when i am in office, i can' use google servers to send mails
and whatever mail i send from within ARM, they are broken.

I can use linaro servers from outside office without any issues and it is never
broken.

>> And for this reason only i push my patches in my public repo all the
>> time, mentioned in cover-letter.
>>
>> http://git.linaro.org/gitweb?p=people/vireshk/linux.git;a=shortlog;h=refs/heads/cpufreq-move-drivers
>
> Okay but you never copied me on the cover letter so I only saw this one
> patch. I will pull your tree and test now.

This series was affecting lots of people and so every patch had a number of
people added as cc. I didn't wanted to add everybody in cc of complete
patchset.

BUT, i have another idea now. The way i used to add people in cc for specific
patches (by editing the patch), i will do the same for cover-letter
too next time.

And so all people will receive relevant patches + cover letter.

--
viresh
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to