All of lore.kernel.org
 help / color / mirror / Atom feed
From: makotouu@gmail.com (Makoto Harada)
To: kernelnewbies@lists.kernelnewbies.org
Subject: How to confirm LOCALVERSION_AUTO config effect
Date: Sat, 06 Sep 2014 01:56:48 +0900	[thread overview]
Message-ID: <5409EB50.5070607@gmail.com> (raw)
In-Reply-To: <5409D163.3050807@bitgrid.net>

Hi, Julius

Thank you so much for your prompt reply.

> 805a6a is tagged as v3.2, and LOCALVERSION_AUTO matches git tags first
> as described in init/Kconfig:
>
>> This will try to automatically determine if the current tree is a
>> release tree by looking for git tags that belong to the current
>> top of tree revision.
Now, I understood.

By resetting one commit from v3.2, then now I got the expected result.

[makoto at vostro linux_mainline][v3.2_test]$ git reset HEAD^
Unstaged changes after reset:
M    Makefile
[makoto at vostro linux_mainline][v3.2_test]$ scripts/setlocalversion
-00105-g8696823-dirty

Thanks !!

Kind Regards,
Makoto Harada

(2014/09/06 0:06), Julius Haertl wrote:
> On 05.09.2014 16:21, Makoto Harada wrote:
>> Dear expert
>>
>> Would someone please teach me how to confirm LOCALVERSION_AUTO config
>> effect ?
>> I built my kernel with LOCALVERSION_AUTO enabled, and boot my PC with
>> the kernel.
>> My expectation is that uname will return the kernel version with git
>> hush version added,
>> however I can not see it as shown below.
>>
>> [makoto at vostro ~]$ zcat /proc/config.gz |grep LOCALVERSION_AUTO
>> CONFIG_LOCALVERSION_AUTO=y
>> [makoto at vostro ~]$ uname -a
>> Linux vostro 3.2.0-makoto-0-dirty #5 SMP Fri Sep 5 22:32:22 JST 2014
>> x86_64 GNU/Linux
>>
>> [makoto at vostro linux_mainline][v3.2]$ git rev-parse --verify HEAD
>> 805a6af8dba5dfdd35ec35dc52ec0122400b2610
>>
>> Any insight would be highly appreciated.
>>
>> Kind Regards,
>> Makoto Harada
>>
>
> Hi Makoto,
>
> 805a6a is tagged as v3.2, and LOCALVERSION_AUTO matches git tags first
> as described in init/Kconfig:
>
>> This will try to automatically determine if the current tree is a
>> release tree by looking for git tags that belong to the current
>> top of tree revision.
> You might have left your changes to the kernel uncommited inside your
> git repository. These uncommited changes produce the -dirty string in
> your kernel name.
>
> The script at scripts/setlocalversion generates the version when you
> have set LOCALVERSION_AUTO=y, so you might also take a look there.
>
> - Julius
>
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

      reply	other threads:[~2014-09-05 16:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-05 14:21 How to confirm LOCALVERSION_AUTO config effect Makoto Harada
2014-09-05 15:06 ` Julius Haertl
2014-09-05 16:56   ` Makoto Harada [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=5409EB50.5070607@gmail.com \
    --to=makotouu@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.