From: Marko Kreen <marko@l-t.ee>
To: Andrew Morton <andrewm@uow.edu.au>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: [patch] preserve symlinked .configs
Date: Thu, 17 May 2001 14:44:42 +0200 [thread overview]
Message-ID: <20010517144442.B1993@l-t.ee> (raw)
In-Reply-To: <3B03BD9D.16662D1C@uow.edu.au>
In-Reply-To: <3B03BD9D.16662D1C@uow.edu.au>; from andrewm@uow.edu.au on Thu, May 17, 2001 at 10:01:33PM +1000
On Thu, May 17, 2001 at 10:01:33PM +1000, Andrew Morton wrote:
> When one has several machines it is nice to keep each
> machine's .config under revision control. Then, on
> each machine,
>
> ln [-s] .config-$(hostname -s) .config
>
> Problem is, `make menuconfig/oldconfig/config' goes and
> removes your link, causing much irritation.
IMHO currect behaviour is the Right Thing. Think of 'cp -al' on
trees. Patching one does not affect another, because patch()
does not modify files, it creates new file. If I use your patch
and have 'cp -al'-d trees which happen to have .config inside,
doing 'make *config' in one tree will affect another. Thats
wrong.
--
marko
prev parent reply other threads:[~2001-05-17 12:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-17 12:01 [patch] preserve symlinked .configs Andrew Morton
2001-05-17 12:44 ` Marko Kreen [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=20010517144442.B1993@l-t.ee \
--to=marko@l-t.ee \
--cc=andrewm@uow.edu.au \
--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