From: chad <yandros@gmail.com>
To: Philip Kaludercic <philipk@posteo.net>
Cc: Arthur Miller <arthur.miller@live.com>,
emacs-devel@gnu.org, Phillip Lord <phillip.lord@newcastle.ac.uk>
Subject: Re: Elpa question: helping with maintainance of a package in Elpa
Date: Tue, 6 Feb 2024 12:17:33 -0500 [thread overview]
Message-ID: <CAO2hHWYyEtmwnMNhxz=Dc+N3WkZ-EYEAtcMQf11jYAsX5xwzyQ@mail.gmail.com> (raw)
In-Reply-To: <87jznhttmu.fsf@posteo.net>
[-- Attachment #1: Type: text/plain, Size: 1020 bytes --]
On Tue, Feb 6, 2024 at 12:02 PM Philip Kaludercic <philipk@posteo.net>
wrote:
> > Do I understand the information in readme file from Elpa repository
> correctly: I
> > don't have to do anything special more than just update Phillips repo
> for the
> > package on GH, since the Cron job uses that URL to update the package
> > automatically if the version is changed? Or do I need to do something
> more to
> > get the new version into Elpa too?
>
> The cron job will synchronise the mirror with the changes made on the GH
> repository. Just note that to release a package, you'll have to bump
> the version tag (any commit changing the line with the version number
> should do).
>
Note (mostly for future search results): "version tag" in this context
means "the line
in the file that looks something like ";; Version: 0.4", rather than
anything having to
do with git tags. (This sometimes confuses people who are/were familiar
with, for
example, Melpa Stable.)
Hope that helps,
~Chad
[-- Attachment #2: Type: text/html, Size: 1471 bytes --]
next prev parent reply other threads:[~2024-02-06 17:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 15:57 Elpa question: helping with maintainance of a package in Elpa Arthur Miller
2024-02-06 17:00 ` Philip Kaludercic
2024-02-06 17:17 ` chad [this message]
2024-02-06 17:24 ` Philip Kaludercic
2024-02-07 13:16 ` Arthur Miller
2024-02-07 13:16 ` Arthur Miller
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='CAO2hHWYyEtmwnMNhxz=Dc+N3WkZ-EYEAtcMQf11jYAsX5xwzyQ@mail.gmail.com' \
--to=yandros@gmail.com \
--cc=arthur.miller@live.com \
--cc=emacs-devel@gnu.org \
--cc=philipk@posteo.net \
--cc=phillip.lord@newcastle.ac.uk \
/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.