From: justinmattock@gmail.com (Justin P. Mattock)
To: linux-arm-kernel@lists.infradead.org
Subject: Query: Patches break with Microsoft exchange server.
Date: Tue, 19 Jun 2018 20:26:41 -0000 [thread overview]
Message-ID: <4C5FCDB4.1080909@gmail.com> (raw)
In-Reply-To: <4C5FCBE1.2080303@st.com>
On 08/09/2010 02:35 AM, 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.
>
> viresh.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
that or just blast them with some cryptology..i.e. pretty sure if your
message was encapsulated(AH/ESP) they couldn't tweak it.. but then
sending such encryption to a public list would require a _key_ on the
other side.. wishful thinking...
(just a thought)...
:-)
Justin P. Mattock
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2018-06-19 20: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
2018-06-19 20:26 ` Justin P. Mattock [this message]
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=4C5FCDB4.1080909@gmail.com \
--to=justinmattock@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).