From: Manuel Giraud via "Emacs development discussions." <emacs-devel@gnu.org>
To: Philip Kaludercic <philipk@posteo.net>
Cc: Manuel Giraud via "Emacs development discussions." <emacs-devel@gnu.org>
Subject: Re: [ELPA] new single file package: mpdired.el
Date: Sat, 09 Mar 2024 14:18:19 +0100 [thread overview]
Message-ID: <87edcjsfvo.fsf@ledu-giraud.fr> (raw)
In-Reply-To: <87wmqcd43u.fsf@posteo.net> (Philip Kaludercic's message of "Fri, 08 Mar 2024 17:29:25 +0000")
Philip Kaludercic <philipk@posteo.net> writes:
> Manuel Giraud <manuel@ledu-giraud.fr> writes:
>
>> Philip Kaludercic <philipk@posteo.net> writes:
>>
>> [...]
>>
>>> OK, this works. If you have signed the CA, then you could set the
>>> version of your package to some pre-release version, using a
>>
>> I don't know what "signed the CA" means in this context.
>
> Contributing packages to GNU ELPA requires you to have signed the FSF
> copyright assignment, see (info "(emacs) Copyright Assignment"), since
> GNU ELPA packages are formally part of Emacs. Assuming you haven't done
> so yet, a maintainer can send you the form.
Ok. So I already have this because I've already contributed to Emacs.
> Git tags aren't needed at all. The ELPA build server relies entirely on
> what the Version tag says.
Ok, I can still have tags on my side.
>> Just to be sure I understand
>> correctly: every version number with a -pre suffix won't update on ELPA?
>
> Yes, more specifically any version which version-to-list can parse and
> returns a version list without any negative elements:
>
> (version-to-list "1.0") ;=> (1 0)
> (version-to-list "1.0pre") ;=> (1 0 -1)
> (version-to-list "1.0git") ;=> (1 0 -4)
>
> see `version-regexp-alist' and keep in mind that the ELPA build server
> uses a few more extensions.
Thanks, all is clear for me now.
--
Manuel Giraud
next prev parent reply other threads:[~2024-03-09 13:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-08 9:26 [ELPA] new single file package: mpdired.el Manuel Giraud via Emacs development discussions.
2024-03-08 10:25 ` Philip Kaludercic
2024-03-08 11:17 ` Manuel Giraud via Emacs development discussions.
2024-03-08 11:26 ` Philip Kaludercic
2024-03-08 12:22 ` Manuel Giraud via Emacs development discussions.
2024-03-08 13:18 ` Philip Kaludercic
2024-03-08 16:25 ` Manuel Giraud via Emacs development discussions.
2024-03-08 16:34 ` Philip Kaludercic
2024-03-08 17:06 ` Manuel Giraud via Emacs development discussions.
2024-03-08 17:29 ` Philip Kaludercic
2024-03-09 13:18 ` Manuel Giraud via Emacs development discussions. [this message]
2024-03-09 13:36 ` Philip Kaludercic
2024-03-10 16:00 ` Manuel Giraud via Emacs development discussions.
2024-03-10 17:03 ` Philip Kaludercic
2024-03-10 17:43 ` Manuel Giraud via Emacs development discussions.
2024-03-10 17:49 ` Manuel Giraud via Emacs development discussions.
2024-03-10 18:03 ` Manuel Giraud via Emacs development discussions.
2024-03-10 18:15 ` Philip Kaludercic
2024-03-10 19:24 ` Eli Zaretskii
2024-03-11 8:44 ` Manuel Giraud via Emacs development discussions.
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=87edcjsfvo.fsf@ledu-giraud.fr \
--to=emacs-devel@gnu.org \
--cc=manuel@ledu-giraud.fr \
--cc=philipk@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.