public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>
Cc: Bill Davidsen <davidsen@tmr.com>, Sam Ravnborg <sam@ravnborg.org>,
	Nicolas Pitre <nico@cam.org>, Andreas Steinmetz <ast@domdv.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: make distclean and make dep??
Date: Mon, 18 Nov 2002 18:25:17 +0100	[thread overview]
Message-ID: <20021118172517.GA6825@mars.ravnborg.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0211181034100.24137-100000@chaos.physics.uiowa.edu>

On Mon, Nov 18, 2002 at 10:36:20AM -0600, Kai Germaschewski wrote:
> But when do you need the "clean + rm .config*" behavior? I don't see that 
> to be such a common case.
> 
> That's why I think two targets are enough, "clean" to remove the files
> generated during the build and "distclean" to remove all other extra stuff
> to. And just keep mrproper to be an alias for distclean, since that's what
> "mrproper" traditionally was (AFAIK, Linus used it that way).

People are used to a mrproper that does NOT delete their editor
backup files and patch rejects. Thats the only arguments against
mrproper=distclean.

The main purpose should be to have a clear and logical
distingush between the two/three.
As it is today people are confused, and there is no consistency - 
especially between architectures.

I'm fine with a change that moves MRPROPER_{DIRS,FILES} to clean - except
.config.
But I'm not fine with the current situation where I have to say goodbye
to all my .rej files + xx~ files just to force a full recompile.

I will do a new patch tomorrow.

	Sam


  parent reply	other threads:[~2002-11-18 17:18 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-13 19:32 make distclean and make dep?? Bill Davidsen
2002-11-13 20:58 ` Sam Ravnborg
2002-11-13 21:14   ` Andreas Steinmetz
2002-11-13 21:29     ` Nicolas Pitre
2002-11-14 15:35       ` Kai Germaschewski
2002-11-14 17:42         ` Sam Ravnborg
2002-11-14 17:47           ` Nicolas Pitre
2002-11-14 21:02           ` Mark Hounschell
2002-11-15  0:31           ` Bill Davidsen
2002-11-15 14:53             ` Sam Ravnborg
2002-11-15 16:01               ` Nicolas Pitre
2002-11-15 16:03                 ` Sam Ravnborg
2002-11-15 19:29               ` Bill Davidsen
2002-11-15 21:25                 ` Sam Ravnborg
2002-11-17  7:49                   ` Bill Davidsen
2002-11-18 16:36                     ` Kai Germaschewski
2002-11-18 17:24                       ` Bill Davidsen
2002-11-18 17:25                       ` Sam Ravnborg [this message]
2002-11-13 23:11     ` Bill Davidsen
2002-11-13 23:09   ` Bill Davidsen
2002-11-14 17:36     ` Sam Ravnborg
  -- strict thread matches above, loose matches on Subject: below --
2002-11-13 19:38 Dan Steele

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=20021118172517.GA6825@mars.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=ast@domdv.de \
    --cc=davidsen@tmr.com \
    --cc=kai@tp1.ruhr-uni-bochum.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nico@cam.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