mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Chris Friesen <cfriesen@nortelnetworks.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: is kernel compilation supposed to change header file timestamps?
Date: Thu, 22 Aug 2002 19:31:56 +0200	[thread overview]
Message-ID: <20020822193156.B1401@mars.ravnborg.org> (raw)
In-Reply-To: <3D65142F.116481FB@nortelnetworks.com>; from cfriesen@nortelnetworks.com on Thu, Aug 22, 2002 at 12:41:19PM -0400

On Thu, Aug 22, 2002 at 12:41:19PM -0400, Chris Friesen wrote:
> 
> I noticed the other day that on a kernel compile, the timestamps of some files are changed.  The
> funny thing is that all the changed ones are header files, but not all header files are modified.
> 
> Is this expected behaviour?
I assume you are compiling a 2.4 kernel, in which case this is expected
behaviour.
For the 2.5 kernel kbuild has been changed such that 
header files are no longer 'touched' during the compile process.

	Sam

      parent reply	other threads:[~2002-08-22 17:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-22 16:41 Chris Friesen
2002-08-22 17:07 ` george anzinger
2002-08-22 17:31 ` Sam Ravnborg [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=20020822193156.B1401@mars.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=cfriesen@nortelnetworks.com \
    --cc=linux-kernel@vger.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

all inboxes | Powered by JetHome®