mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: DervishD <lkml@dervishd.net>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	torvalds@osdl.org, patrakov@ums.usu.ru
Subject: Re: [PATCH] Fix console utf8 composing (F)
Date: Tue, 21 Mar 2006 11:30:53 +0100	[thread overview]
Message-ID: <20060321103053.GB1700@DervishD> (raw)
In-Reply-To: <Pine.LNX.4.61.0603202200030.23653@yvahk01.tjqt.qr>

    Hi Jan :)

 * Jan Engelhardt <jengelh@linux01.gwdg.de> dixit:
> > * Jan Engelhardt <jengelh@linux01.gwdg.de> dixit:
> >> can we have the patch[2] from this[1] thread merged? I have not yet
> >> heard back from Alexander since [3]. Plus we're lacking a
> >> Signed-off-by so far for [2]. What to do?
> >
> >    Can it be backported to 2.4.x or does it use many 2.6.xisms? I'm
> >very interested in the issue because otherwise I'm going to add a
> >terminal emulator for virtual consoles to my vcinit project. I don't
> >use X and I want to use utf8 in a virtual console...
> 
> Maybe. I just found that it does not apply cleanly anymore to
> 2.6.16 so I am going to fix that first and submit a rediffed
> version. If I then feel like investing more time, maybe I can do it
> for 2.4.32 too, but no promises. I am running out of gcc3 systems.

    I can betatest it if you want, but anyway this is a reason as
good as any to switch my box to 2.6.x

    I don't find 2.6.x stable enough to run it on my box, but the
development model won't change in the near future, so I think I'll
have to live with that. I would love a backport, of course, but I
prefer to have an utf8 capable console.

    Thanks a lot for the patch :)

    Raúl Núñez de Arenas Coronado

-- 
Linux Registered User 88736 | http://www.dervishd.net
http://www.pleyades.net & http://www.gotesdelluna.net
It's my PC and I'll cry if I want to... RAmen!

  reply	other threads:[~2006-03-21 10:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-20 19:54 Jan Engelhardt
2006-03-20 20:05 ` DervishD
2006-03-20 21:04   ` Jan Engelhardt
2006-03-21 10:30     ` DervishD [this message]
2006-03-20 23:19 ` J.A. Magallon
2006-03-21 17:28   ` Jan Engelhardt
2006-03-21  3:56 ` Alexander E. Patrakov
2006-03-22 15:56   ` Jan Engelhardt
2006-03-25 18:32     ` Jan Engelhardt

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=20060321103053.GB1700@DervishD \
    --to=lkml@dervishd.net \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patrakov@ums.usu.ru \
    --cc=torvalds@osdl.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®