From: Glenn Morris <rgm@gnu.org>
To: Alex <agrambot@gmail.com>
Cc: lunaryorn@gmail.com, Stefan Monnier <monnier@IRO.UMontreal.CA>,
14967@debbugs.gnu.org, npostavs@users.sourceforge.net
Subject: bug#14967: 24.3.50; package-delete deletes by trashing?
Date: Mon, 12 Jun 2017 16:32:22 -0400 [thread overview]
Message-ID: <ocr2yp6j6x.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <87r2yp2dmw.fsf@gmail.com> (Alex's message of "Mon, 12 Jun 2017 13:45:59 -0600")
Alex wrote:
> Is that a good idea for new behaviour that results in potential data
> loss (from the view of a user that expects `package-delete' to trash
> files rather than outright deleting them)? It might be easy to gloss
> over an entry in NEWS, after all.
IMO there's no real potential for data loss, since you can just
reinstall the package from its source. (I assume this is what people do
in practice, rather than un-trashing.) Although "source is no longer
available" is in theory possible, in practice I don't think it's a real
concern.
next prev parent reply other threads:[~2017-06-12 20:32 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-27 10:30 bug#14967: 24.3.50; package-delete deletes by trashing? Sebastian Wiesner
2013-07-29 22:02 ` Glenn Morris
2013-07-30 10:51 ` Sebastian Wiesner
2013-07-30 14:21 ` Stefan Monnier
2013-07-30 14:40 ` Sebastian Wiesner
2013-07-30 15:14 ` Stefan Monnier
2016-08-05 23:40 ` npostavs
2016-09-03 4:06 ` Alex
2017-06-11 23:58 ` npostavs
2017-06-12 3:26 ` Alex
2017-06-12 14:27 ` Eli Zaretskii
2017-06-12 16:03 ` Glenn Morris
2017-06-12 16:33 ` Eli Zaretskii
2017-06-12 16:56 ` Glenn Morris
2017-06-12 17:02 ` Stefan Monnier
2017-06-14 2:54 ` Richard Stallman
2017-06-12 17:04 ` Eli Zaretskii
2017-06-12 17:17 ` Stefan Monnier
2017-06-12 19:45 ` Alex
2017-06-12 20:32 ` Glenn Morris [this message]
2017-06-13 3:50 ` Alex
2017-06-19 18:47 ` Glenn Morris
2017-06-12 19:37 ` Alex
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=ocr2yp6j6x.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=14967@debbugs.gnu.org \
--cc=agrambot@gmail.com \
--cc=lunaryorn@gmail.com \
--cc=monnier@IRO.UMontreal.CA \
--cc=npostavs@users.sourceforge.net \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.