linux-kernel - [Question] Restore previous "local tag" behaviour

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <1de9eccd-8570-3b69-4be2-347e862bcc33@mailbox.org>
Date:   Mon, 27 Mar 2023 17:44:07 +0000
From:   Tor Vic <torvic9@...lbox.org>
To:     Masahiro Yamada <masahiroy@...nel.org>
Cc:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>
Subject: [Question] Restore previous "local tag" behaviour

Hi,

When I'm building my kernels, I used to tag my personal releases with a 
similar annotated tag commit as with vanilla kernel, just appending 
"-tv" or similar to it, i.e. "v6.3-rc4" becomes "v6.3-rc4-tv".

This has worked just fine so far, but...

Since commit 6ab7e1f95e96f0c688ae132b0e9a16c0f206689d ("setlocalversion: 
use only the correct release tag for git-describe"), this is not taken 
into account anymore, it uses the "git describe" tag instead of using 
the actually tagged commit as "kernelrelease".

Is there a way to restore the previous behaviour without having to 
revert this (and preceding) commits?

I know that we can disable CONFIG_LOCALVERSION_AUTO=y and append 
directly to CONFIG_LOCALVERSION, but maybe someone knows how to use the 
"old" way of using tags...?

In other words, when I have a local tag, I want "kernelrelease" to use 
just that tag, and when I don't tag anything, it should just use the 
standard "git describe" tag.

For the moment I have just reverted the related commits as they don't 
serve any purpose for my needs.

Cheers,

Tor Vic