linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felipe Contreras <felipe.contreras@gmail.com>
To: viresh kumar <viresh.kumar@st.com>, git@vger.kernel.org
Cc: "linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Query: Patches break with Microsoft exchange server.
Date: Wed, 11 Aug 2010 01:04:08 +0300	[thread overview]
Message-ID: <AANLkTinxwRFLUibJECm0c3_oL5mYRkmscsw-xXgAHSTe@mail.gmail.com> (raw)
In-Reply-To: <4C5F9B25.8080401@st.com>

On Mon, Aug 9, 2010 at 9:07 AM, viresh kumar <viresh.kumar@st.com> wrote:
> Mail server in ST has recently changed and now we have Microsoft
> exchange server. We are using thunderbird as mail client.
> What we observed with this server is that patch are broken now while
> sending as well as receiving. Tabs are replaced by spaces and may
> be some other too which we haven't observed.
>
> Has anybody found a solution to this kind of issues? Are there any
> workarounds possible?

Same in Nokia. I wrote a script to fix exchange's crap, but I also
noticed some quoted-printable mails didn't get converted, so the
easiest would be to tell git to always send quoted-printable.

git folks: any chance of getting that feature to git send-email?

-- 
Felipe Contreras

  parent reply	other threads:[~2010-08-10 22:04 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-09  6:07 Query: Patches break with Microsoft exchange server viresh kumar
2010-08-09  6:42 ` Justin P. Mattock
2010-08-09  6:55   ` viresh kumar
2010-08-09  7:32     ` Justin P. Mattock
2010-08-09  6:49 ` Uwe Kleine-König
2010-08-09  6:56   ` viresh kumar
2010-08-09  7:19     ` Valeo de Vries
2010-08-09  7:47       ` viresh kumar
2010-08-09  9:00         ` Valeo de Vries
2010-08-09  9:01     ` Matti Aarnio
2010-08-09  9:35       ` viresh kumar
2010-08-09  9:43         ` 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-09 22:12                     ` Valeo de Vries
2010-08-09 22:24                       ` Justin P. Mattock
2010-08-11 14:05                   ` Geert Uytterhoeven
2010-08-10  9:22         ` Gadiyar, Anand
2010-08-10  9:26           ` viresh kumar
2010-08-09 10:02       ` David Woodhouse
2018-06-19 20:42         ` Willy Tarreau
2010-08-09 14:19 ` Richard Cochran
2010-08-09 14:34   ` Valeo de Vries
2010-08-10 22:04 ` Felipe Contreras [this message]
2010-08-11  7:01   ` viresh kumar
2010-08-11 10:11     ` Valeo de Vries
2010-08-11 10:53       ` viresh kumar
2010-08-11 11:38         ` Wouter Simons
2010-08-11 13:33       ` Justin P. Mattock
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  1:02 ` Gururaja Hebbar K R

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=AANLkTinxwRFLUibJECm0c3_oL5mYRkmscsw-xXgAHSTe@mail.gmail.com \
    --to=felipe.contreras@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viresh.kumar@st.com \
    /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).