From: Stefan Kangas <stefankangas@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
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 11:28:58 +0000 [thread overview]
Message-ID: <CADwFkmmNCRMy0ZoAh0v96cF-Cn+o+iy2rmeKDCXQPXe77rSPSA@mail.gmail.com> (raw)
In-Reply-To: <jwv7cnvpiyh.fsf-monnier+emacs@gnu.org>
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> The (Non)GNU ELPA tarballs are built from `elpa.git` and `nongnu.git`,
> not from the upstream repositories, and currently those do not
> contain upstream tags.
>
> And since those repos contain many packages, the upstream tags need to
> be renamed or moved to a different namespace to avoid conflicts between
> tag names in different packages.
I'm starting to wonder if Philip's idea to use signed git commits might
work better for our purposes.
Would signed tags give us something that signed commits wouldn't?
next prev parent reply other threads:[~2023-10-10 11:28 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 [this message]
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
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=CADwFkmmNCRMy0ZoAh0v96cF-Cn+o+iy2rmeKDCXQPXe77rSPSA@mail.gmail.com \
--to=stefankangas@gmail.com \
--cc=66414@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=philipk@posteo.net \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).