[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5A47E75E594F054BAF48C5E4FC4B92AB032401D8F0@dbde02.ent.ti.com>
Date: Tue, 10 Aug 2010 14:52:20 +0530
From: "Gadiyar, Anand" <gadiyar@...com>
To: viresh kumar <viresh.kumar@...com>,
Matti Aarnio <matti.aarnio@...iler.org>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>
Subject: RE: Query: Patches break with Microsoft exchange server.
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.
- Anand
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists