From: Brett Gilio <brettg@posteo.net>
To: Kyle Meyer <kyle@kyleam.com>
Cc: Guix-devel <guix-devel@gnu.org>, 38529@debbugs.gnu.org
Subject: Re: bug#38529: Make --ad-hoc the default for guix environment proposed deprecation mechanism
Date: Tue, 17 Dec 2019 14:22:15 +0000 (UTC) [thread overview]
Message-ID: <4ee893ad-b489-4e98-b716-e418cd3b8049@localhost> (raw)
In-Reply-To: <87pngncc0n.fsf@kyleam.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=UTF-8, Size: 596 bytes --]
Dec 17, 2019 7:34:17 AM Kyle Meyer :
> Gábor Boskovits writes:
>
>
> > Konrad Hinsen ezt írta (id?pont: 2019. dec.
> > 17., Ke 7:52):
> >
> [...]
>
> >
> > > How about a more drastic measure: deprecate "guix environment" and
> > > introduce a new subcommand with the desired new behaviour?
> > >
> > >
> > That is also the other option I was thinking about. Do you have any good
> > idea in mind as how to call it? Of course the classic guix environment2
> > comes to my mind, but it does not look very appealing to me.
> >
>
> Perhaps "guix env"?
>
+1 for guix env
next prev parent reply other threads:[~2019-12-17 14:22 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87eexeu8mo.fsf@ambrevar.xyz>
[not found] ` <CAJ3okZ3WnG87m=jQw08M9ER+=9FS0NVx=uALHK_-4LuD50KhvA@mail.gmail.com>
2019-12-12 11:23 ` Make --ad-hoc the default for guix environment proposed deprecation mechanism Gábor Boskovits
2019-12-12 16:47 ` bug#38529: " zimoun
2019-12-12 20:54 ` Gábor Boskovits
2019-12-13 12:02 ` zimoun
2019-12-13 16:27 ` Gábor Boskovits
2019-12-13 16:32 ` zimoun
2019-12-13 16:41 ` Gábor Boskovits
2019-12-14 18:11 ` Hartmut Goebel
2019-12-16 22:09 ` Ludovic Courtès
2019-12-17 6:49 ` Konrad Hinsen
2019-12-17 9:14 ` Gábor Boskovits
2019-12-17 13:33 ` Kyle Meyer
2019-12-17 14:22 ` Brett Gilio [this message]
2019-12-17 22:30 ` Bengt Richter
2019-12-17 23:21 ` Bengt Richter
2019-12-17 17:07 ` zimoun
2019-12-18 9:43 ` Konrad Hinsen
2019-12-18 13:09 ` zimoun
2019-12-20 11:24 ` Konrad Hinsen
2019-12-20 12:03 ` zimoun
2019-12-20 21:08 ` Ricardo Wurmus
2019-12-23 9:28 ` Danny Milosavljevic
2020-01-02 9:49 ` Andy Wingo
2019-12-18 20:55 ` Arne Babenhauserheide
2019-12-19 11:30 ` zimoun
2019-12-19 21:39 ` Arne Babenhauserheide
2019-12-19 22:40 ` zimoun
2019-12-20 1:37 ` Arne Babenhauserheide
2019-12-20 11:40 ` zimoun
2019-12-20 23:02 ` Arne Babenhauserheide
2019-12-21 0:04 ` zimoun
2019-12-20 21:12 ` Ricardo Wurmus
2019-12-21 15:18 ` Konrad Hinsen
2019-12-19 16:31 ` Deprecating ‘guix environment’? Ludovic Courtès
2019-12-19 22:48 ` zimoun
2019-12-20 11:17 ` Konrad Hinsen
2019-12-20 13:21 ` zimoun
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=4ee893ad-b489-4e98-b716-e418cd3b8049@localhost \
--to=brettg@posteo.net \
--cc=38529@debbugs.gnu.org \
--cc=guix-devel@gnu.org \
--cc=kyle@kyleam.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.
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).