mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: trini@kernel.crashing.org
Cc: olh@suse.de, marcelo@conectiva.com.br,
	linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: Re: [PATCH] net/802/Makefile
Date: Mon, 26 Nov 2001 21:26:58 -0800 (PST)	[thread overview]
Message-ID: <20011126.212658.82514202.davem@redhat.com> (raw)
In-Reply-To: <20011126221012.C13091@cpe-24-221-152-185.az.sprintbbd.net>
In-Reply-To: <20011126203527.C31937@suse.de> <20011126.114045.102135510.davem@redhat.com> <20011126221012.C13091@cpe-24-221-152-185.az.sprintbbd.net>

   From: Tom Rini <trini@kernel.crashing.org>
   Date: Mon, 26 Nov 2001 22:10:12 -0700

   On Mon, Nov 26, 2001 at 11:40:45AM -0800, David S. Miller wrote:
   > No, because it is writable by the user in every kernel source tree I
   > have ever seen, the change makes no sense.
   
   You haven't tried a BitKeeper tree then.  You have to explicitly get
   write permission.
   
That doesn't make any sense to me.

Firstly, the *.c file should be newer than the template it is
generated from, so the rule which tries to write the file should
never run if your file timestamps are setup correctly.  So get the
timestamps correct in your bitkeeper trees :)

Secondly, there is no reason the version control system should prevent
a file from being writable to the user who owns the file, especially
in a case like this.

In fact, this is one of the things that makes my balls hurt when I
download source tarballs from some places.  I have to chmod +w the
files to edit them just to make hack test local changes that I don't
care if anyone ever sees ever again.  At that point I'm fighting
whatever source control system those sources came from.

  parent reply	other threads:[~2001-11-27  5:27 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-26 13:06 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 [this message]
2001-11-27  6:12       ` Keith Owens
2001-11-27  6:18       ` David S. Miller
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.212658.82514202.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    --cc=olh@suse.de \
    --cc=torvalds@transmeta.com \
    --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 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®