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

On Thu, Nov 14, 2002 at 09:35:53AM -0600, Kai Germaschewski wrote:
> I think there's good reasons for both distclean and mrproper, distclean is
> the standard target which most projects use, and mrproper is the
> traditional Linux kernel target. So I would vote for keeping them both
> (and share a common help entry).
> 
> What I don't see is why we would need different semantics, though, 
> anybody?
How about the following:
clean	Delete all intermidiate files, including symlinks and modversions
mrproper	clean + deletes .config and .config.old
distclean	mrproper + all editor backup, patch backup files

In other words a more powerfull clean compared to today.
The difference between clean and mrproper is then _only_ the configuration
files. That easy to explain, and thats easy to understand. Today only
very few people know the difference, and simply save their config,
and do make mrproper.

I have many times seen people do something like:
cp .config xxx
make mrproper
mv xxx .config

No need for that, when make clean deletes enough.

Only caveat is that people are forced to wait for the modversion stuff,
but to my understanding Rusty is making that step obsolete soon.
Did I miss something obvious?

	Sam

  reply	other threads:[~2002-11-14 17:35 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-13 19:32 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 [this message]
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
2002-11-13 23:11     ` Bill Davidsen
2002-11-13 23:09   ` Bill Davidsen
2002-11-14 17:36     ` Sam Ravnborg
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=20021114174246.GB10723@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

all inboxes | Powered by JetHome®