From: Sam Ravnborg <sam@ravnborg.org>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Ulf Magnusson <ulfalizer@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Randy Dunlap <rdunlap@infradead.org>,
Michal Marek <michal.lkml@markovi.net>
Subject: Re: [RFC PATCH 1/1] kconfig: drop localization support
Date: Thu, 24 May 2018 17:41:01 +0200 [thread overview]
Message-ID: <20180524154101.GA12927@ravnborg.org> (raw)
In-Reply-To: <CAK7LNARata6s_Dm_ykVNX2o15psE0LyuFvXQFESa7=n58s+nxg@mail.gmail.com>
Hi Masahiro
>
> When I applied this, I added the following fix-up.
>
>
>
> diff --git a/scripts/kconfig/.gitignore b/scripts/kconfig/.gitignore
> index 54266f3..0aabc1d 100644
> --- a/scripts/kconfig/.gitignore
> +++ b/scripts/kconfig/.gitignore
> @@ -2,7 +2,6 @@
> # Generated files
> #
> *.moc
> -*.mo
>
> #
> # configuration programs
>
>
>
>
> .mo is no longer generated.
>
> It was added by
> commit c26dd719a5b9d94d12211f2d101bd7dffb7f9f1f
>
>
>
> Please double-check if it is OK.
I left it as I was not sure where the .mo extension came from.
And trying out the different frontends did not generate
any .mo files (I tried with a kernel before my patches).
So I assume the .mo extension was added because it is
often seen in combination with .pot files,
and not because the kernel actually generated such file.
See https://make.wordpress.org/polyglots/handbook/glossary/#mo-files
for a short description of the .mo files.
In other words - the fixup is correct. Thanks!
Sam
prev parent reply other threads:[~2018-05-24 15:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-22 19:49 [RFC PATCH 1/1] kconfig: drop localization support Sam Ravnborg
[not found] ` <CAK7LNAQUF6YbHRTJOtQ9F91M-iqF1U+PemDAbsdx3qzcqg4Ufw@mail.gmail.com>
2018-05-23 2:23 ` Masahiro Yamada
2018-05-23 4:46 ` Sam Ravnborg
2018-05-24 14:21 ` Masahiro Yamada
2018-05-24 15:41 ` Sam Ravnborg [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=20180524154101.GA12927@ravnborg.org \
--to=sam@ravnborg.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.lkml@markovi.net \
--cc=rdunlap@infradead.org \
--cc=ulfalizer@gmail.com \
--cc=yamada.masahiro@socionext.com \
/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