public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] bmp_logo: Check return value of fread()
Date: Mon, 27 Apr 2009 20:01:47 -0400	[thread overview]
Message-ID: <200904272001.48083.vapier@gentoo.org> (raw)
In-Reply-To: <1240876395.11057.126.camel@localhost.localdomain>

On Monday 27 April 2009 19:53:15 Peter Tyser wrote:
> 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.

which is reasonable and common behavior imo

> 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?

`git format-patch` did the right thing and converted the e-mail body to 
base64.  if you do the format-patch again and edit the resulting file, you'll 
see it.

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

there isnt a good one which is why i keep whining at Wolfgang to let it 
through.  you can either not use a unicode environment at all (which sucks), 
or just remember this kind of thing and always check the output of git's 
format-patch before sending it.  then when you notice, review the files to 
figure out where the unicode is coming from -- most of the time it's the 
commit message, but sometimes it comes from comments in the source code.  so 
you have to keep your eyes open for umlauts and such (????).

i havent checked, but using extended codepages will probably also result in 
base64 encoding ...
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20090427/90e6cfe1/attachment.pgp 

  reply	other threads:[~2009-04-28  0:01 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
2009-04-28  0:01       ` Mike Frysinger [this message]
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=200904272001.48083.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --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