public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Stefan Richter <stefanr@s5r6.in-berlin.de>,
	mgarski@post.pl, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Convert files to UTF-8 and some cleanups
Date: Mon, 14 May 2007 22:25:09 +0200	[thread overview]
Message-ID: <20070514202509.GA1515@stusta.de> (raw)
In-Reply-To: <Pine.LNX.4.61.0705142209090.9570@yvahk01.tjqt.qr>

On Mon, May 14, 2007 at 10:10:20PM +0200, Jan Engelhardt wrote:
> 
> On May 14 2007 20:06, Stefan Richter wrote:
> >On 14 May, Jan Engelhardt wrote:
> >> I've had a quick look at it...
> >> 
> >>   * Copyright (C) 2004 Nokia Corporation
> >>   * Written by Tony Lindgren <tony@atomide.com>
> >> - * Major cleanups by Juha YrjXlX <juha.yrjola@nokia.com>
> >> + * Major cleanups by Juha Yrjölä <juha.yrjola@nokia.com>
> >> 
> >> 
> >> I thought I already fixed that part with the patch from
> >> http://lkml.org/lkml/2007/1/8/222
> >> 
> >> but of course I can't tell without getting at that .bz2 thing I
> >> sent back them. Anyone know of a site that stores these too?
> >
> >http://marc.info/?l=linux-kernel&m=116828781409931
> 
> I checked.
> Now that kinda sucks, everyone does the same job over and over,
> I did a ton of utf8 fixes and they did not get applied. (Granted,
> I did not cc Andrew, Linus or trivial).

If you had Cc'ed trivial they would now be in Linus' tree...

> 	Jan

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2007-05-14 20:25 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-13 23:54 [PATCH] Convert files to UTF-8 and some cleanups Marcin Garski
2007-05-14  0:08 ` Marcin Garski
2007-05-14 14:14   ` Stefan Richter
2007-05-14 15:28     ` John Anthony Kazos Jr.
2007-05-14 16:25       ` Stefan Richter
2007-05-14 16:41         ` Stefan Richter
2007-05-14 16:46         ` Adrian Bunk
2007-05-14 17:17           ` Stefan Richter
2007-05-14 17:48     ` Jan Engelhardt
2007-05-14 18:06       ` Stefan Richter
2007-05-14 20:10         ` Jan Engelhardt
2007-05-14 20:25           ` Adrian Bunk [this message]
2007-05-14 20:36             ` Jan Engelhardt
2007-05-14 20:41               ` Adrian Bunk
2007-05-14 21:14                 ` Jan Engelhardt
2007-05-14 22:20                   ` Stefan Richter
2007-05-15  8:05                     ` Jan Engelhardt
2007-05-15 16:23                   ` [PATCH] Pekka Pietikainen goes UTF-8 Pekka Pietikainen
2007-05-16  6:05                     ` H. Peter Anvin
2007-05-16  6:55                       ` Jan Engelhardt
2007-05-16 15:11                         ` H. Peter Anvin
2007-05-16 16:38                       ` [PATCH] Pekka Pietikainen goes UTF-8 (try #2) Pekka Pietikainen
2007-05-16 17:16                         ` Pekka Pietikainen
2007-05-16 17:53                         ` Björn Steinbrink

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=20070514202509.GA1515@stusta.de \
    --to=bunk@stusta.de \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgarski@post.pl \
    --cc=stefanr@s5r6.in-berlin.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