From: Stefan Monnier via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: help-gnu-emacs@gnu.org
Cc: gnu-emacs-sources@gnu.org
Subject: Re: [GNU ELPA] Denote version 0.6.0
Date: Thu, 01 Sep 2022 11:33:35 -0400 [thread overview]
Message-ID: <jwvh71rglj3.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: 87fshb86hb.fsf@posteo.net
> I've been wondering if sending an Email to the maintainer or in this
> case a mailing list (as is the case with Denote, since I've recommended
> doing so) makes sense to begin with. Wouldn't they know if a release
> had been made?
The maintainers normally know that they requested a new release, but not
that this request has been acted upon successfully.
Stefan
prev parent reply other threads:[~2022-09-01 15:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <85wnaounvf.fsf@elpa.gnu.org>
2022-09-01 0:50 ` [GNU ELPA] Denote version 0.6.0 Protesilaos Stavrou
2022-09-01 1:23 ` Stefan Monnier via GNU Emacs source code postings and patches
2022-09-01 15:22 ` Philip Kaludercic
2022-09-01 15:33 ` Stefan Monnier via Users list for the GNU Emacs text editor [this message]
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/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvh71rglj3.fsf-monnier+emacs@gnu.org \
--to=help-gnu-emacs@gnu.org \
--cc=gnu-emacs-sources@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).