From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from asavdk3.altibox.net ([109.247.116.14]:50174 "EHLO asavdk3.altibox.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S967064AbeEXPlG (ORCPT ); Thu, 24 May 2018 11:41:06 -0400 Date: Thu, 24 May 2018 17:41:01 +0200 From: Sam Ravnborg Subject: Re: [RFC PATCH 1/1] kconfig: drop localization support Message-ID: <20180524154101.GA12927@ravnborg.org> References: <20180522194928.GA29900@ravnborg.org> <20180523044609.GA23800@ravnborg.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: linux-kbuild-owner@vger.kernel.org List-ID: To: Masahiro Yamada Cc: Ulf Magnusson , Linux Kernel Mailing List , Greg Kroah-Hartman , Linux Kbuild mailing list , Randy Dunlap , Michal Marek 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