Re: [Patch] Non-ASCII chars in visor.c messages

From: Pavel Machek (pavel@suse.cz)
Date: Wed Jul 23 2003 - 06:16:34 EST

Next message: Sergey S. Kostyliov: "Re: 2.4.22pre6aa1"
Previous message: Pavel Machek: "Re: 2.6.0-test1: CPUFreq not working, can't find sysfs interface"
In reply to: Greg KH: "Re: [Patch] Non-ASCII chars in visor.c messages"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Hi!

> > What do you think about it?
>
> I don't think it's really needed. Why change this, syslog can't handle
> this? It works for me...
>

It would not work here. Make it us-ascii.

-- Pavel Written on sharp zaurus, because my Velo1 broke. If you have Velo you don't need...

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

Next message: Sergey S. Kostyliov: "Re: 2.4.22pre6aa1"
Previous message: Pavel Machek: "Re: 2.6.0-test1: CPUFreq not working, can't find sysfs interface"
In reply to: Greg KH: "Re: [Patch] Non-ASCII chars in visor.c messages"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Wed Jul 23 2003 - 22:00:49 EST