All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Kai Germaschewski <kai@germaschewski.name>,
	Sam Ravnborg <sam@ravnborg.org>
Subject: .version keeps being updated
Date: Tue, 9 Jan 2007 10:20:57 +0100	[thread overview]
Message-ID: <20070109102057.c684cc78.khali@linux-fr.org> (raw)

Hi all,

Since 2.6.20-rc1 or so, running "make" always builds a new kernel with
an incremented version number, whether there has actually been any
change done to the code or configuration or not. This increases the
build time quite a bit.

I've tracked it down to include/linux/compile.h always being updated,
and this is because .version is updated. I couldn't find what is
causing .version to be updated each time though. Can anybody help
there? Was this change made on purpose or is this a bug which we should
fix?

Thanks,
-- 
Jean Delvare

             reply	other threads:[~2007-01-09  9:20 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-09  9:20 Jean Delvare [this message]
2007-01-09  9:32 ` .version keeps being updated Gene Heskett
2007-01-09 17:05 ` Andrey Borzenkov
2007-01-09 20:44   ` Jean Delvare
2007-01-09 21:31     ` Andrew Morton
2007-01-09 23:21       ` Linus Torvalds
2007-01-09 23:25         ` Andrew Morton
2007-01-09 23:33           ` David Miller
2007-01-09 23:39           ` Andi Kleen
2007-01-10  1:43           ` Herbert Poetzl
2007-01-10  8:53           ` Jean Delvare
2007-01-10 16:52           ` Martin J. Bligh
2007-01-10 17:05             ` Jean Delvare
2007-01-10 11:31         ` Jan Engelhardt
2007-01-10 13:45     ` Roman Zippel
2007-01-10 16:01       ` Olaf Hering
2007-01-10 17:10       ` Jean Delvare
2007-01-10 19:02         ` Linus Torvalds
2007-01-10 19:31           ` Olaf Hering
2007-01-10 20:02             ` Olaf Hering
2007-01-10 22:56               ` Jan Engelhardt
2007-01-10 23:35                 ` Segher Boessenkool
2007-01-11 13:27                   ` Jan Engelhardt
2007-01-11 13:55                     ` Andreas Schwab
2007-01-11 17:39                       ` Segher Boessenkool
2007-01-11 18:01                         ` Jan Engelhardt
2007-01-10 21:33             ` Linus Torvalds
2007-01-10 19:32           ` Linus Torvalds
2007-01-10 21:20             ` Andy Whitcroft
2007-01-11 10:56             ` Andy Whitcroft
2007-01-11 12:38           ` Roman Zippel
2007-01-11 13:05             ` Andy Whitcroft
2007-01-11 16:47             ` Linus Torvalds
2007-01-09 21:55 ` Luca Tettamanti
2007-01-10  7:34   ` Jean Delvare
2007-01-09 23:25 ` Willy Tarreau

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=20070109102057.c684cc78.khali@linux-fr.org \
    --to=khali@linux-fr.org \
    --cc=kai@germaschewski.name \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.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.