public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Tor Vic <torvic9@mailbox.org>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>
Subject: [Question] Restore previous "local tag" behaviour
Date: Mon, 27 Mar 2023 17:44:07 +0000	[thread overview]
Message-ID: <1de9eccd-8570-3b69-4be2-347e862bcc33@mailbox.org> (raw)

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

             reply	other threads:[~2023-03-27 17:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-27 17:44 Tor Vic [this message]
2023-04-01  6:22 ` [Question] Restore previous "local tag" behaviour Masahiro Yamada
2023-04-05 13:25   ` torvic9
2023-04-05 14:16     ` torvic9

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=1de9eccd-8570-3b69-4be2-347e862bcc33@mailbox.org \
    --to=torvic9@mailbox.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@kernel.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