public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Peter Tyser <ptyser@xes-inc.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] bmp_logo: Check return value of fread()
Date: Mon, 27 Apr 2009 18:53:15 -0500	[thread overview]
Message-ID: <1240876395.11057.126.camel@localhost.localdomain> (raw)
In-Reply-To: <200904271941.35614.vapier@gentoo.org>

On Mon, 2009-04-27 at 19:41 -0400, Mike Frysinger wrote:
> On Monday 27 April 2009 19:18:21 Wolfgang Denk wrote:
> > In message Peter Tyser wrote:
> > > <base64 stuff>
> > ...
> >
> > Please do not post base64 encoded messages.  Next time I will ignore
> > such patches.
> 
> it's due to unicode yet again:
> 
> > > bmp_logo.c: In function `main':
> 
> those ticks are probably the left & right unicode ticks that pretty much all 
> GNU tools use.  it's pretty hard for people to catch these things in the 
> normal flow of git usage considering using a unicode locale setting and a GNU 
> system is by and far the norm.

Ahhhh, thanks for the enlightenment - that makes sense.  I use urxvt and
pasted the output of a gcc warning in the commit message.

The copies cc-ed to myself come through just fine as utf-8 fwiw.  Does
that imply the denx.de servers convert unicode messages to base64?

In general, what's the proper workaround so things like this don't
happen?

Peter

  reply	other threads:[~2009-04-27 23:53 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-24 20:59 [U-Boot] [PATCH] bmp_logo: Check return value of fread() Peter Tyser
2009-04-27 23:18 ` Wolfgang Denk
2009-04-27 23:41   ` Mike Frysinger
2009-04-27 23:53     ` Peter Tyser [this message]
2009-04-28  0:01       ` Mike Frysinger
2009-04-28  5:21       ` Wolfgang Denk
2009-04-28  9:11         ` Detlev Zundel
2009-04-28 12:58           ` Mike Frysinger
2009-04-28 17:06             ` Detlev Zundel
2009-04-28 17:15               ` Mike Frysinger
2009-04-30 14:00                 ` Detlev Zundel
2009-04-30 15:43                   ` Mike Frysinger
2009-04-28 15:06         ` Peter Tyser
2009-04-28 15:49           ` Mike Frysinger
2009-04-28 15:57             ` Peter Tyser
2009-04-28 17:03               ` Mike Frysinger
2009-04-28 17:22           ` Mike Frysinger
2009-04-28 18:01             ` Peter Tyser

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=1240876395.11057.126.camel@localhost.localdomain \
    --to=ptyser@xes-inc.com \
    --cc=u-boot@lists.denx.de \
    /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