mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Helge Hafting <helgehaf@aitel.hist.no>
To: Sam Ravnborg <sam@ravnborg.org>, linux-kernel@vger.kernel.org
Subject: Re: clean before or after dep?
Date: Mon, 09 Sep 2002 09:29:36 +0200	[thread overview]
Message-ID: <3D7C4DE0.2D1C9909@aitel.hist.no> (raw)
In-Reply-To: <20020908205011.A1671@mars.ravnborg.org>

Sam Ravnborg wrote:

> With the 2.5 kernel, if make clean or make mrproper is ever _required_
> I would say you had triggered an error in the kernel build system.
> 
> > - theory: a clean should be done after a failing build so that
> >   a subsequent build won't use the results of the failing build.
> Should not be needed with the build system in the 2.5 kernel.

Make clean is nice to have for a couple of occations:

1. Before making a tar.bz2 of the tree as a backup.  Why 
   waste space on .o files?
   A backup is useful for a number of reasons, such as
   before testing a mix of patches that might
   interferre badly.  Or even patches for another version. 
   Getting the tree again takes time.

2. The pc hardware clock screwed up again and timestamps
   are spread all over past and future :-(  Make clean time.

Helge Hafting

      parent reply	other threads:[~2002-09-09  7:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-08  1:51 D. Hugh Redelmeier
2002-09-08 13:13 ` Alan Cox
2002-09-08 13:31   ` Joe Kellner
2002-09-08 13:53     ` Dr. David Alan Gilbert
2002-09-09 18:03       ` Thunder from the hill
2002-09-08 14:53   ` Sam Ravnborg
2002-09-08 17:51     ` Thomas Molina
2002-09-08 18:09   ` D. Hugh Redelmeier
2002-09-08 18:50     ` Sam Ravnborg
2002-09-08 18:54       ` jbradford
2002-09-08 19:23         ` Sam Ravnborg
2002-09-09  7:29       ` Helge Hafting [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=3D7C4DE0.2D1C9909@aitel.hist.no \
    --to=helgehaf@aitel.hist.no \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.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®