From: Vincent Legoll <vincent.legoll@gmail.com>
To: Mark H Weaver <mhw@netris.org>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>,
"Jeremiah@pdp10.guru" <Jeremiah@pdp10.guru>
Subject: Re: Cleaning up make clean's behavior
Date: Sun, 3 Jun 2018 08:29:17 +0200 [thread overview]
Message-ID: <CAEwRq=ou5iBUto9afibTA4pNMsHf9RozdPJ43f52frwXi6Mgtg@mail.gmail.com> (raw)
In-Reply-To: <87bmcsd859.fsf@netris.org>
[-- Attachment #1: Type: text/plain, Size: 1129 bytes --]
Hello
On Sunday, June 3, 2018, Mark H Weaver <mhw@netris.org> wrote:
> I don't think we should change "make clean" to delete files in the
> working directory that were not created by our build system.
>
> I, for one, keep many files of notes and draft patches in my Guix
> working directory. I've been doing this for years. If "make clean"
> were suddenly changed to delete all of these files, I would lose data
> and probably be very angry.
>
> I happened to see this message, but if I had been focused on other
> things, I might well have missed it. It's not practical for us to
> ensure that everyone is warned about this proposed change, so there's no
> way for us to avoid the risk that valuable user data would be deleted.
>
> Therefore, we should reject this proposal.
>
> In general, we should be *very* reluctant to delete files that we know
> nothing about. We should be reluctant to do it even if there were a
> very compelling reason for it. Simply wanting to clean up to avoid
> unsightly clutter falls far short of a compelling reason.
>
> Thoughts?
>
> Mark
>
>
+1 totally agree
--
Vincent Legoll
[-- Attachment #2: Type: text/html, Size: 1464 bytes --]
next prev parent reply other threads:[~2018-06-03 6:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-02 16:23 Cleaning up make clean's behavior Jeremiah
2018-06-02 16:46 ` Nils Gillmann
2018-06-02 16:54 ` Gábor Boskovits
2018-06-03 0:29 ` Mark H Weaver
2018-06-03 6:29 ` Vincent Legoll [this message]
2018-06-04 11:36 ` Ludovic Courtès
2018-06-10 6:41 ` Chris Marusich
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAEwRq=ou5iBUto9afibTA4pNMsHf9RozdPJ43f52frwXi6Mgtg@mail.gmail.com' \
--to=vincent.legoll@gmail.com \
--cc=Jeremiah@pdp10.guru \
--cc=guix-devel@gnu.org \
--cc=mhw@netris.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).