mkinitrd unification across distributions
 help / color / mirror / Atom feed
From: Harald Hoyer <harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: "Amadeusz Żołnowski" <aidecoe-2qtfh70TtYba5EbDDlwbIw@public.gmane.org>
Cc: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] 10i18n: README corrected
Date: Wed, 21 Jul 2010 13:40:11 +0200	[thread overview]
Message-ID: <4C46DC9B.80105@redhat.com> (raw)
In-Reply-To: <20100713101355.26a2ecb8@etiriah>

pushed both

On 07/13/2010 10:13 AM, Amadeusz Żołnowski wrote:
> ---
>   modules.d/10i18n/README |    6 +++---
>   1 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/modules.d/10i18n/README b/modules.d/10i18n/README
> index dd84881..09cb642 100644
> --- a/modules.d/10i18n/README
> +++ b/modules.d/10i18n/README
> @@ -53,7 +53,7 @@ runtime:
>       CONTRANS - see description of '-m' parameter in setfont manual
>       UNIMAP - see description of '-u' parameter in setfont manual
>
> -The following are appended to EXT_KEYMAPS:
> +The following are appended to EXT_KEYMAPS only during build time:
>
>       UNIKEYMAP
>       GRP_TOGGLE
> @@ -120,5 +120,5 @@ file (the same where you put mappings).
>   3. Kernel parameters
>
>   If you create generic initramfs you can set up i18n by kernel
> -parameters using variables listed in 2.1.  The recommended minimum is:
> -SYSFONT, KEYMAP and UNICODE.
> +parameters using variables listed in 2.1. (expect of UNIKEYMAP
> +and GRP_TOGGLE) The recommended minimum is: SYSFONT, KEYMAP and UNICODE.

      reply	other threads:[~2010-07-21 11:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-13  7:58 [PATCH] README for 10i18n module Amadeusz Żołnowski
2010-07-13  8:13 ` [PATCH] 10i18n: README corrected Amadeusz Żołnowski
2010-07-21 11:40   ` Harald Hoyer [this message]

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=4C46DC9B.80105@redhat.com \
    --to=harald-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=aidecoe-2qtfh70TtYba5EbDDlwbIw@public.gmane.org \
    --cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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