MIME-Version: 1.0
References: <a10e1319-b631-6d3b-5e1d-b07223350502@igalia.com>
In-Reply-To: <a10e1319-b631-6d3b-5e1d-b07223350502@igalia.com>
From:   Masahiro Yamada <masahiroy@kernel.org>
Date:   Fri, 10 Mar 2023 09:51:54 +0900
Message-ID: <CAK7LNAQmXwpEpY84-fdLiwALSFLUEkfsOHejbqy33c6ceM=4Tw@mail.gmail.com>
Subject: Re: About the .scmversion removal (commit f6e09b07cc12)
To:     "Guilherme G. Piccoli" <gpiccoli@igalia.com>
Cc:     linux-kbuild@vger.kernel.org, nathan@kernel.org,
        rasmus.villemoes@prevas.dk,
        Nick Desaulniers <ndesaulniers@google.com>, nicolas@fjasle.eu,
        linux-kernel <linux-kernel@vger.kernel.org>,
        "Guilherme G. Piccoli" <kernel@gpiccoli.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

On Fri, Mar 10, 2023 at 6:15=E2=80=AFAM Guilherme G. Piccoli
<gpiccoli@igalia.com> wrote:
>
> Hi Masahiro / all, I was rebuilding the kernel today, just adding some
> debug statements, when I noticed a lot of stuff got built again. I was
> using ".scmversion" to prevent UTS version changes, so only affected
> files got indeed rebuilt.
>
> After commit f6e09b07cc12 ("kbuild: do not put .scmversion into the
> source tarball"), seems this file is automatically deleted and I'm not
> sure how should I proceed to continue with the same behavior.
>
> Apologies if this is a silly question, any advice is much appreciated!
> Also, I've CCed all the emails from [0], so apologies if anybody looped
> here shouldn't be CCed.


Not a silly question, but .scmversion was intended for source
package creation (deb, rpm) in my understanding.

If you want to use a fixed string for the UTS version,
please pass KERNELRELEASE=3D<some-string> to the build command line.


--=20
Best Regards
Masahiro Yamada