From: Leo Famulari <leo@famulari.name>
To: 41010@debbugs.gnu.org
Cc: rprior@protonmail.com
Subject: [bug#41010] Upgrade Oil to 0.8.pre4
Date: Sat, 2 May 2020 15:16:22 -0400 [thread overview]
Message-ID: <20200502191622.GB22384@jasmine.lan> (raw)
In-Reply-To: <87sggjfdef.fsf@nckx>
[-- Attachment #1: Type: text/plain, Size: 394 bytes --]
On Sat, May 02, 2020 at 01:23:30AM +0200, Tobias Geerinckx-Rice via Guix-patches via wrote:
> I agree with the name change, although I'm unaware of why ‘oil-shell’ was
> originally chosen.
No serious reason. I thought it was close the upstream name (it's the
GitHub organization name) and that 'oil' was a bit short for something
so obscure. Feel free to change it to 'oil' though.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-05-02 19:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-01 20:01 [bug#41010] Rename & upgrade oil-shell Ryan Prior via Guix-patches via
2020-05-01 21:01 ` [bug#41010] Upgrade Oil to 0.8.pre4 Ryan Prior via Guix-patches via
2020-05-01 23:23 ` Tobias Geerinckx-Rice via Guix-patches via
2020-05-01 23:33 ` Tobias Geerinckx-Rice via Guix-patches via
2020-05-02 4:02 ` Ryan Prior via Guix-patches via
2020-05-15 17:10 ` Ryan Prior via Guix-patches via
2020-05-15 18:31 ` Tobias Geerinckx-Rice via Guix-patches via
2020-05-16 11:20 ` Tobias Geerinckx-Rice via Guix-patches via
2020-05-17 6:14 ` Ryan Prior via Guix-patches via
2020-05-02 19:16 ` Leo Famulari [this message]
2020-05-28 23:38 ` [bug#41010] [PATCH 0/1] Updated patch for 0.8.pre5 Ryan Prior via Guix-patches via
2020-05-28 23:38 ` [bug#41010] [PATCH 1/1] gnu: oil: Update to 0.8.pre5 Ryan Prior via Guix-patches via
2020-05-29 4:48 ` bug#41010: [PATCH 0/1] Updated patch for 0.8.pre5 Tobias Geerinckx-Rice via Guix-patches via
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=20200502191622.GB22384@jasmine.lan \
--to=leo@famulari.name \
--cc=41010@debbugs.gnu.org \
--cc=rprior@protonmail.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 external index
https://git.savannah.gnu.org/cgit/guix.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.