From: Ricardo Wurmus <rekado@elephly.net>
To: gwl-devel@gnu.org
Subject: Preparing for a new release
Date: Sat, 08 Feb 2020 13:39:47 +0100 [thread overview]
Message-ID: <87h801p818.fsf@elephly.net> (raw)
Hi,
I’ve pushed a bunch of the previously discussed improvements to the
repository and also added more documentation. Please also note the
TODO.org file, which is for ideas and plans that may not necessarily be
flully fleshed out.
I’ll leave the load-path + inferior magic for a later release. This is
hairy stuff and I’d rather have us mull this over for a little while
longer before committing to an implementation.
Your comments on the code and the documentation, and also your
experience reports are very welcome!
--
Ricardo
next reply other threads:[~2020-02-08 12:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-08 12:39 Ricardo Wurmus [this message]
2020-02-08 20:38 ` Preparing for a new release Kyle Meyer
2020-02-08 21:50 ` Ricardo Wurmus
2020-02-09 13:00 ` Ricardo Wurmus
2020-02-09 23:33 ` zimoun
2020-02-10 1:25 ` Kyle Meyer
2020-02-10 7:34 ` zimoun
2020-02-10 6:31 ` Ricardo Wurmus
2020-02-10 7:43 ` zimoun
2020-02-10 21:28 ` Ricardo Wurmus
2020-02-10 23:43 ` zimoun
2020-02-11 9:39 ` Ricardo Wurmus
2020-02-11 9:34 ` Ricardo Wurmus
2020-02-11 15:37 ` 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://www.guixwl.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h801p818.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=gwl-devel@gnu.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.
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).