From: Dave Airlie <airlied@gmail.com>
To: Dave Airlie <airlied@gmail.com>,
"Martin Schlemmer [c]" <azarah@nosferatu.za.org>,
Sam Ravnborg <sam@ravnborg.org>, Andrew Morton <akpm@osdl.org>,
torvalds@osdl.org,
Linux Kernel Mailing Lists <linux-kernel@vger.kernel.org>
Subject: timestamps in kernel was Re: [PATCH 2.6.9-bk7] Select cpio_list or source directory for initramfs image updates [u]
Date: Wed, 27 Oct 2004 14:55:42 +1000 [thread overview]
Message-ID: <21d7e99704102621553310abe8@mail.gmail.com> (raw)
In-Reply-To: <20041027062148.GA12123@mars.ravnborg.org>
>
> Could you try to list the places - maybe they do not all make sense.
Here is my current list in things that directly affect me:
sound/core/info.c contains __DATE__ to tell what date it was compiled
on, I'm not sure this is really needed.
usr/gen_init_cpio.c uses time(NULL) to set mtimes,
scripts/Makefile.lib uses gzip with no -n flag
I can supply patches to get rid of these if people think they are a
good/bad idea...
I also hack scripts/mkcompile_h so it never changes for me (this one
is acceptable as it is very obvious that you have to do it...)
Dave.
next prev parent reply other threads:[~2004-10-27 4:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200410200849.i9K8n5921516@mail.osdl.org>
2004-10-23 12:06 ` [PATCH 2.6.9-bk7] Select cpio_list or source directory for initramfs image updates [u] Martin Schlemmer [c]
2004-10-24 10:08 ` Andrew Morton
2004-10-24 13:59 ` Martin Schlemmer [c]
2004-10-24 22:26 ` Sam Ravnborg
2004-10-26 22:12 ` Sam Ravnborg
2004-10-26 21:07 ` Martin Schlemmer [c]
2004-10-26 23:15 ` Sam Ravnborg
2004-10-26 21:36 ` Martin Schlemmer [c]
2004-10-27 4:09 ` Dave Airlie
2004-10-27 6:21 ` Sam Ravnborg
2004-10-27 4:55 ` Dave Airlie [this message]
2004-10-27 18:44 ` Martin Schlemmer [c]
2004-10-30 23:43 ` Sam Ravnborg
2004-10-31 10:36 ` Martin Schlemmer [c]
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=21d7e99704102621553310abe8@mail.gmail.com \
--to=airlied@gmail.com \
--cc=akpm@osdl.org \
--cc=azarah@nosferatu.za.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=torvalds@osdl.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.