From: viresh.kumar@st•com (viresh kumar)
To: linux-arm-kernel@lists•infradead.org
Subject: Query: Patches break with Microsoft exchange server.
Date: Tue, 10 Aug 2010 14:56:31 +0530 [thread overview]
Message-ID: <4C611B47.4090709@st.com> (raw)
In-Reply-To: <5A47E75E594F054BAF48C5E4FC4B92AB032401D8F0@dbde02.ent.ti.com>
On 8/10/2010 2:52 PM, Gadiyar, Anand wrote:
> viresh kumar wrote:
>> > On 8/9/2010 2:31 PM, Matti Aarnio wrote:
>>> > > On Mon, Aug 09, 2010 at 12:26:24PM +0530, viresh kumar wrote:
>>>>> > >> >
>>>>> > >> > I missed this information in my last mail. We are using git send-email for
>>>>> > >> > sending patches. As patches will go through Microsoft exchange server only,
>>>>> > >> > so they are broken.
>>>>> > >> >
>>> > > Let your boss complain to your IT keepers.
>>> > > "These are Machine-to-Machine messages, they must not be modified!"
>>> > >
>>> > >
>>> > > It would probably be "against corporate policy" to use gmail for these emails...
>>> > >
>> >
>> > We got one solution: Upgrade Exchange server to SP2.
>> > Lets see if our IT department does this upgradation.
>> >
> Upgrading the Exchange server worked for us a couple of years ago. At least
> git-send-email works okay now, but Outlook is horribly broken.
>
> You could use gmail/others and send externally. Adding an explicit
> "From :" line in the patch can still give you credits to your official
> email address.
>
Thanks Anand.
Lets see if our IT support team manages to upgrade to SP2 or not.
viresh.
next prev parent reply other threads:[~2010-08-10 9:26 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-19 20:23 Query: Patches break with Microsoft exchange server viresh kumar
2010-08-09 14:19 ` Richard Cochran
2010-08-10 22:04 ` Felipe Contreras
2010-08-11 7:01 ` viresh kumar
2010-08-11 15:46 ` Jeffrey Hundstad
2010-08-11 15:58 ` David Woodhouse
2010-08-11 16:16 ` Jeffrey Hundstad
2010-08-11 16:18 ` Avery Pennarun
2010-08-11 16:30 ` David Woodhouse
2010-08-11 16:39 ` Avery Pennarun
2010-08-12 4:41 ` viresh kumar
2010-08-16 0:32 ` Gururaja Hebbar K R
2018-06-19 20:24 ` Justin P. Mattock
2018-06-19 20:24 ` viresh kumar
2018-06-19 20:24 ` Justin P. Mattock
2018-06-19 20:24 ` Uwe Kleine-König
2018-06-19 20:24 ` viresh kumar
2018-06-19 20:26 ` Matti Aarnio
2018-06-19 20:26 ` viresh kumar
2010-08-10 9:22 ` Gadiyar, Anand
2010-08-10 9:26 ` viresh kumar [this message]
2018-06-19 20:26 ` Justin P. Mattock
2010-08-09 14:35 ` Mihai Donțu
2010-08-09 17:55 ` Justin P. Mattock
2010-08-09 18:15 ` Mihai Donțu
2010-08-09 18:53 ` Justin P. Mattock
2010-08-09 21:28 ` David Woodhouse
2010-08-09 21:56 ` Justin P. Mattock
2010-08-11 14:05 ` Geert Uytterhoeven
2018-06-19 20:26 ` David Woodhouse
2018-06-19 20:42 ` Willy Tarreau
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C611B47.4090709@st.com \
--to=viresh.kumar@st$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox