From: ison <ison@airmail.cc>
To: Jesse Gibbons <jgibbons2357@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: When is it appropriate to rename a file?
Date: Sun, 16 Jun 2019 12:21:47 -0600 [thread overview]
Message-ID: <20190616182146.asihmoclm4yghh6p@cf0> (raw)
In-Reply-To: <20190615214344.5fc6a013@gmail.com>
I'm not by any means the one who should be answering this question, but just
wanted to throw the idea out there that perhaps such things are best saved for
major version changes.
Because it would require every user to rethink the modules they're using in
their system config.scm (and possibly packages that aren't installed with
"system" would have to be re-installed manually).
So perhaps on Guix 2.0, 3.0, etc. is when it would be acceptable to do house
cleaning like renaming modules.
Just a thought.
next prev parent reply other threads:[~2019-06-16 18:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-16 3:43 When is it appropriate to rename a file? Jesse Gibbons
2019-06-16 18:21 ` ison [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-06-17 17:18 Jesse Gibbons
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=20190616182146.asihmoclm4yghh6p@cf0 \
--to=ison@airmail.cc \
--cc=help-guix@gnu.org \
--cc=jgibbons2357@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).