From: Phil Blundell <pb@pbcl.net>
To: Ross Burton <ross.burton@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] wipe-sysroot: explain what is being deleted and require confirmation
Date: Fri, 01 Nov 2013 21:04:43 +0000 [thread overview]
Message-ID: <1383339883.8901.42.camel@x121e.pbcl.net> (raw)
In-Reply-To: <1383335233-12366-1-git-send-email-ross.burton@intel.com>
On Fri, 2013-11-01 at 19:47 +0000, Ross Burton wrote:
> Instead of rushing into deleting entire directory trees without any warning,
> print the directories and files that will be deleted and require confirmation
> from the user (via --force) that they want files to be deleted.
"--force" seems like a bit of an odd name for an argument that you have
to supply in order for the script to do anything useful. Why would the
user be running a script named "wipe-sysroot" if they didn't want the
sysroot to be deleted?
p.
next prev parent reply other threads:[~2013-11-01 21:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-01 19:47 [PATCH] wipe-sysroot: explain what is being deleted and require confirmation Ross Burton
2013-11-01 21:04 ` Phil Blundell [this message]
2013-11-01 23:21 ` Burton, Ross
2013-11-02 16:19 ` Phil Blundell
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=1383339883.8901.42.camel@x121e.pbcl.net \
--to=pb@pbcl.net \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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