From: "Ludovic Courtès" <ludo@gnu.org>
To: Andy Wingo <wingo@igalia.com>, "Mark H. Weaver" <mhw@netris.org>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Releasing 2.2.5?
Date: Thu, 06 Jun 2019 10:44:44 +0200 [thread overview]
Message-ID: <87d0jrp0g3.fsf@gnu.org> (raw)
Hello comrades!
What would you think of releasing ‘stable-2.2’ as 2.2.5?
It’s great if you can do it, Mark, but otherwise I can do it.
Thanks,
Ludo’.
next reply other threads:[~2019-06-06 8:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-06 8:44 Ludovic Courtès [this message]
2019-06-06 8:56 ` Releasing 2.2.5? Nala Ginrut
2019-06-06 16:48 ` Mike Gran
2019-06-16 7:48 ` Distributed verification of release tarballs using Guix? (was Re: Releasing 2.2.5?) Mark H Weaver
2019-06-16 21:23 ` Ludovic Courtès
2019-06-16 22:17 ` Mark H Weaver
2019-06-17 8:44 ` Ludovic Courtès
2019-06-19 2:48 ` Mark H Weaver
2019-06-20 10:54 ` Ludovic Courtès
2019-06-20 21:53 ` Mark H Weaver
2019-06-21 9:27 ` Neil Jerram
2019-07-25 4:15 ` Rob Browning
2019-07-25 8:58 ` Ricardo Wurmus
2019-07-25 15:26 ` Rob Browning
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.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d0jrp0g3.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@gnu.org \
--cc=mhw@netris.org \
--cc=wingo@igalia.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).