From: "David S. Miller" <davem@redhat.com>
To: kaos@ocs.com.au
Cc: trini@kernel.crashing.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net/802/Makefile
Date: Mon, 26 Nov 2001 22:18:55 -0800 (PST) [thread overview]
Message-ID: <20011126.221855.102041585.davem@redhat.com> (raw)
In-Reply-To: <12077.1006841524@kao2.melbourne.sgi.com>
In-Reply-To: <20011126.212658.82514202.davem@redhat.com> <12077.1006841524@kao2.melbourne.sgi.com>
From: Keith Owens <kaos@ocs.com.au>
Date: Tue, 27 Nov 2001 17:12:04 +1100
The source repository (whether BK or any other system) is not the
problem. You can get the timestamps right in the source but the moment
you generate and ship a diff then you lose control of timestamps. See
the long screed below about the problems with shipping generated files,
from kbuild-2.5.txt.
Even after reading this I don't understand why defkeymap.c gets
special treatment just because it requires external tools to generate.
If the timestamps get messed up, it's going to try to regerenerate the
file with loadkeys whether you have it or not.
At best, I'd be happy to take a patch which commented out the rule
which tries to generate net/802/cl2llc.c but not one which will chmod
it. Because the latter only makes sense if we are now deciding to do
this for _every_ such case in the tree.
next prev parent reply other threads:[~2001-11-27 6:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-26 13:06 [PATCH] net/802/Makefile Olaf Hering
2001-11-26 13:24 ` Olaf Hering
2001-11-26 13:32 ` Christoph Hellwig
2001-11-26 13:54 ` Keith Owens
2001-11-26 16:56 ` Alan Cox
2001-11-26 15:13 ` Andreas Schwab
2001-11-26 17:14 ` Marcelo Tosatti
2001-11-26 19:20 ` David S. Miller
2001-11-26 19:35 ` Olaf Hering
2001-11-26 19:40 ` David S. Miller
2001-11-27 5:10 ` Tom Rini
2001-11-27 5:26 ` David S. Miller
2001-11-27 6:12 ` Keith Owens
2001-11-27 6:18 ` David S. Miller [this message]
2001-11-27 6:28 ` Keith Owens
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=20011126.221855.102041585.davem@redhat.com \
--to=davem@redhat.com \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=trini@kernel.crashing.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.