From: Sergey B Kirpichev <skirpichev@gmail.com>
To: Michael Shigorin <mike@altlinux.org>
Cc: 39651@debbugs.gnu.org
Subject: bug#39651: /software/guile/docs/ lacks 3.0
Date: Tue, 18 Feb 2020 10:02:25 +0300 [thread overview]
Message-ID: <20200218070225.GA27297@note> (raw)
In-Reply-To: <20200217211119.GQ4527@imap.altlinux.org>
On Tue, Feb 18, 2020 at 12:11:19AM +0300, Michael Shigorin wrote:
> a forum commenter has brought my attention to the fact that
> https://www.gnu.org/software/guile/docs/ page mentions "Preview
> Reference Manual for unreleased Guile 2.2 (development branch)"
> and fails to mention 3.0 completely (even if it's been released recently).
No. I was mentioned, that you provide link to the old
release (as a stable version). Guile docs seems fine for
me: https://www.gnu.org/software/guile/learn/
next prev parent reply other threads:[~2020-02-18 7:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-17 21:11 bug#39651: /software/guile/docs/ lacks 3.0 Michael Shigorin
2020-02-18 7:02 ` Sergey B Kirpichev [this message]
2020-02-19 20:40 ` Andy Wingo
2020-02-19 21:07 ` Michael Shigorin
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=20200218070225.GA27297@note \
--to=skirpichev@gmail.com \
--cc=39651@debbugs.gnu.org \
--cc=mike@altlinux.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).