From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] understanding --depclean
Date: Wed, 12 Nov 2008 09:08:53 +0000 [thread overview]
Message-ID: <20081112090853.714c7933@digimed.co.uk> (raw)
In-Reply-To: <491A62D8.4030300@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 389 bytes --]
On Tue, 11 Nov 2008 23:00:08 -0600, Dale wrote:
> Be very careful with --depclean. It can really mess up something if you
> are not watching close.
That may have been the case some time ago, but depclean is much safer
now. Notice that the warning at the start of its output has disappeared
now?
--
Neil Bothwick
All new: Parts not interchangeable with previous model.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-11-12 9:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-12 4:41 [gentoo-user] understanding --depclean Michael P. Soulier
2008-11-12 5:00 ` Dale
2008-11-12 9:08 ` Neil Bothwick [this message]
2008-11-12 17:13 ` Dale
2008-11-12 21:12 ` Neil Bothwick
2008-11-13 19:29 ` Dale
2008-11-12 9:19 ` KH
2008-11-12 17:15 ` Dale
2008-11-12 9:48 ` Vladimir Rusinov
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=20081112090853.714c7933@digimed.co.uk \
--to=neil@digimed.co.uk \
--cc=gentoo-user@lists.gentoo.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