From: Chris Chabot <chabotc@xs4all.nl>
To: davidsen@tmr.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Why 'mrproper'?
Date: Wed, 07 Aug 2002 15:18:27 +0200 [thread overview]
Message-ID: <3D511E23.8020902@xs4all.nl> (raw)
In-Reply-To: Pine.LNX.4.33.0208070851230.2421-100000@iccarus.tmr.com
It was named such at the time, as a 'cleaning agent' comparible to 'Mr
Muscle', etc.. Thus mrproper _realy_ cleans the kernel tree ;-)
-- Chris
Bill Davidsen wrote:
>Having started out on the four floppy MCC "distribution" of Linux,
>building kernels clean with 'make distclean,' can someone provide a quick
>historical note as to what mrproper buys? A quick look at the tree after
>each didn't tell me much.
>
>
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at http://www.tux.org/lkml/
>
>
next prev parent reply other threads:[~2002-08-07 13:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-07 12:55 Why 'mrproper'? Bill Davidsen
2002-08-07 13:18 ` Chris Chabot [this message]
2002-08-07 13:58 ` DevilKin
2002-08-07 15:08 ` Thunder from the hill
2002-08-07 17:30 ` Heinz Diehl
2002-08-07 14:13 ` Tomas Szepe
2002-08-07 13:32 ` Matti Aarnio
2002-08-07 23:12 ` Bill Davidsen
2002-08-07 23:23 ` Thunder from the hill
2002-08-07 13:46 ` Sean Neakums
2002-08-07 17:00 ` Andries Brouwer
2002-08-07 17:13 ` Thunder from the hill
2002-08-07 18:51 ` Andries Brouwer
2002-08-07 20:07 ` Thunder from the hill
2002-08-07 21:07 ` Andries Brouwer
2002-08-07 23:28 ` Bill Davidsen
2002-08-09 17:47 ` Kelsey Hudson
2002-08-09 17:57 ` kernel memory swap Imran Badr
2002-08-09 19:43 ` Richard B. Johnson
2002-08-09 23:19 ` Gilad Ben-Yossef
-- strict thread matches above, loose matches on Subject: below --
2002-08-14 16:25 Why 'mrproper'? Joerg Pommnitz
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=3D511E23.8020902@xs4all.nl \
--to=chabotc@xs4all.nl \
--cc=davidsen@tmr.com \
--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