From: Philip Kaludercic <philipk@posteo.net>
To: Stefan Monnier via GNU Emacs source code postings and patches
<gnu-emacs-sources@gnu.org>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, help-gnu-emacs@gnu.org
Subject: Re: [GNU ELPA] Denote version 0.6.0
Date: Thu, 01 Sep 2022 15:22:24 +0000 [thread overview]
Message-ID: <87fshb86hb.fsf@posteo.net> (raw)
In-Reply-To: <jwvfshbc2jf.fsf-monnier+emacs@gnu.org> (Stefan Monnier via's message of "Wed, 31 Aug 2022 21:23:30 -0400")
Stefan Monnier via GNU Emacs source code postings and patches
<gnu-emacs-sources@gnu.org> writes:
>> Just to note that this is an automated message from GNU ELPA. I am not
>> in control of it. Here are the complete release notes:
>> https://protesilaos.com/codelog/2022-08-31-denote-0-6-0/
>>
>> If I find time, I will check with elpa.git to see if we can have some
>> more control over these messages.
What would you like to change?
> There isn't much control over it, currently.
> Basically the control limits itself to
> - the first line in the main <pkg>.el file.
> - the "news" which can come from the `News:` section or forom the file
> specified via the `:news` property in the package's spec.
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?
> Stefan
next prev parent reply other threads:[~2022-09-01 15:22 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 [this message]
2022-09-01 15:33 ` Stefan Monnier via Users list for the GNU Emacs text editor
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=87fshb86hb.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=gnu-emacs-sources@gnu.org \
--cc=help-gnu-emacs@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.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.