all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: 66414@debbugs.gnu.org, philipk@posteo.net, yantar92@posteo.net
Subject: bug#66414: GNU ELPA: Require signed tags to release new package versions
Date: Tue, 10 Oct 2023 09:24:24 -0400	[thread overview]
Message-ID: <jwva5sqoblk.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <CADwFkmk=hwHi+iWMU28S7ScBPW4XDpSiFPTg-yVxX0wmRGqoNw@mail.gmail.com> (Stefan Kangas's message of "Tue, 10 Oct 2023 13:18:34 +0000")

> I see no fundamental reason why we should need to choose, but my
> assumption was that supporting only one or the other would be less work.

True.  But there are regular requests to support releasing versions from
tags rather than from commits (regardless of signing), so I think we
will eventually support both.


        Stefan






      reply	other threads:[~2023-10-10 13:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-09  7:15 bug#66414: GNU ELPA: Require signed tags to release new package versions Stefan Kangas
2023-10-09  8:32 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-09  8:37   ` Stefan Kangas
2023-10-09  9:01 ` Philip Kaludercic
2023-10-09  9:30   ` Stefan Kangas
2023-10-09  9:39     ` Philip Kaludercic
2023-10-09  9:44       ` Stefan Kangas
2023-10-09 21:52 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-10 11:28   ` Stefan Kangas
2023-10-10 13:07     ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-10 13:18       ` Stefan Kangas
2023-10-10 13:24         ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=jwva5sqoblk.fsf-monnier+emacs@gnu.org \
    --to=bug-gnu-emacs@gnu.org \
    --cc=66414@debbugs.gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=philipk@posteo.net \
    --cc=stefankangas@gmail.com \
    --cc=yantar92@posteo.net \
    /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.