mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stanislav Brabec <utx@penguin.cz>
To: Pavel Machek <pavel@ucw.cz>
Cc: rpurdie@rpsys.net, lenz@cs.wisc.edu,
	kernel list <linux-kernel@vger.kernel.org>,
	Dirk@Opfer-Online.de, arminlitzel@web.de,
	Cyril Hrubis <metan@ucw.cz>,
	thommycheck@gmail.com,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	dbaryshkov@gmail.com, omegamoon@gmail.com, eric.y.miao@gmail.com,
	zaurus-devel@www.linuxtogo.org, Andrew Morton <akpm@osdl.org>
Subject: Re: [patch] fix strange characters in zaurus gpio .desc
Date: Thu, 07 Jan 2010 23:31:23 +0100	[thread overview]
Message-ID: <1262903483.5722.7.camel@utx.utx.cz> (raw)
In-Reply-To: <20100107203104.GA22681@elf.ucw.cz>

Pavel Machek wrote:
> From: Cyril Hrubis <metan@ucw.cz>
>     
> Somehow,
Some = my Evolution Mail

I remember that I prepared a patch and fixed capitalization of these
strings in the mail body in the last minute before sending.

> strange characters made their way zaurus gpio .desc
> fields. Fix it.
>     
> Signed-off-by: Pavel Machek <pavel@ucw.cz>

Acked-by: Stanislav Brabec <utx@penguin.cz>

Hint: If you use Evolution Mail for sending mails, never edit anything
inside inlined patch and never use old mail as a template, otherwise
Evolution Mail will include invisible characters to your mail.

Let's see whether it is fixed in the evolution-2.28.


________________________________________________________________________
Stanislav Brabec
http://www.penguin.cz/~utx/zaurus


  reply	other threads:[~2010-01-07 22:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-07 20:31 Pavel Machek
2010-01-07 22:31 ` Stanislav Brabec [this message]
2010-01-08  1:44   ` Eric Miao
2010-01-08  1:57     ` Eric Miao

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=1262903483.5722.7.camel@utx.utx.cz \
    --to=utx@penguin.cz \
    --cc=Dirk@Opfer-Online.de \
    --cc=akpm@osdl.org \
    --cc=arminlitzel@web.de \
    --cc=dbaryshkov@gmail.com \
    --cc=eric.y.miao@gmail.com \
    --cc=lenz@cs.wisc.edu \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=metan@ucw.cz \
    --cc=omegamoon@gmail.com \
    --cc=pavel@ucw.cz \
    --cc=rpurdie@rpsys.net \
    --cc=thommycheck@gmail.com \
    --cc=zaurus-devel@www.linuxtogo.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

all inboxes | Powered by JetHome®