From: Adam Porter <adam@alphapapa.net>
To: emacs-devel <emacs-devel@gnu.org>
Subject: [ELPA] Use :release-branch for plz.el
Date: Sat, 16 Dec 2023 07:02:43 -0600 [thread overview]
Message-ID: <42ebf138-55e9-4103-bd2e-a564e3d43037@alphapapa.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 410 bytes --]
Hi Stefan, Philip, et al,
Please see the attached patch which sets the release branch for plz.el.
This will allow me to make small, bug-fix version releases from the
stable branch while the next version is in development on the master branch.
BTW, after having done this for a few packages now, this seems to me to
be the best practice. It might be worth recommending this for new packages.
Thanks,
Adam
[-- Attachment #2: 0001-elpa-packages-plz-release-branch-stable.patch --]
[-- Type: text/x-patch, Size: 830 bytes --]
From f5541803a174f677e703d921b875e7875da19662 Mon Sep 17 00:00:00 2001
From: Adam Porter <adam@alphapapa.net>
Date: Sat, 16 Dec 2023 06:59:01 -0600
Subject: [PATCH] * elpa-packages: (plz) :release-branch "stable"
This allows bug-fix versions to be released from "stable" while the
next stable release is in development on "master".
---
elpa-packages | 1 +
1 file changed, 1 insertion(+)
diff --git a/elpa-packages b/elpa-packages
index 612bc676cd..ffa211b80f 100644
--- a/elpa-packages
+++ b/elpa-packages
@@ -550,6 +550,7 @@
:manual-sync t)
(pinentry :url "https://github.com/ueno/pinentry-el.git")
(plz :url "https://github.com/alphapapa/plz.el.git"
+ :release-branch "stable"
:ignored-files ("LICENSE")
:doc "README.org")
(plz-see :url "https://github.com/astoff/plz-see.el"
--
2.30.2
next reply other threads:[~2023-12-16 13:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-16 13:02 Adam Porter [this message]
2023-12-17 8:38 ` [ELPA] Use :release-branch for plz.el Philip Kaludercic
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=42ebf138-55e9-4103-bd2e-a564e3d43037@alphapapa.net \
--to=adam@alphapapa.net \
--cc=emacs-devel@gnu.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.
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).