From: Philip Kaludercic <philipk@posteo.net>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: [nongnu] main 23c23ad: * elpa-packages (smartparens): Add package
Date: Thu, 19 Aug 2021 09:23:29 +0000 [thread overview]
Message-ID: <875yw1u6su.fsf@posteo.net> (raw)
In-Reply-To: <87a6lsv008.fsf@posteo.net> (Philip Kaludercic's message of "Sun, 08 Aug 2021 08:00:55 +0000")
Philip Kaludercic <philipk@posteo.net> writes:
> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>
>> Philip Kaludercic [2021-08-07 19:11:09] wrote:
>>> + ("smartparens" :url "https://github.com/Fuco1/smartparens"
>>> + :ignored-files ("dev" "doc" "images" "test")
>>> + ;; See https://github.com/Fuco1/smartparens/releases/tag/1.11.0
>>> + :version-map ((nil "1.11.0" "4873352b5d0a1c5142658122de1b6950b8fe7e4d")))
>>
>> Thanks Philip,
>>
>> Even better than this URL would be a link to an issue/bugreport
>> requesting the version number be added in the file.
>
> I'll update both the smartparens and the haskell-mode package
> specification to add those links.
It has been requested to remove haskell-mode for now, because the
maintainers are not sure how their release procedure interacts with
ELPA:
https://github.com/haskell/haskell-mode/issues/1755#issuecomment-896127958
Would there be any issue in just commenting the specification out?
>>
>> Stefan
>>
As a side-note, would be make sense to extend elpa-admin to handle git
tags if requested?
--
Philip Kaludercic
next prev parent reply other threads:[~2021-08-19 9:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210807231108.10378.42095@vcs0.savannah.gnu.org>
[not found] ` <20210807231109.E658220BD3@vcs0.savannah.gnu.org>
2021-08-08 3:24 ` [nongnu] main 23c23ad: * elpa-packages (smartparens): Add package Stefan Monnier
2021-08-08 8:00 ` Philip Kaludercic
2021-08-19 9:23 ` Philip Kaludercic [this message]
2021-08-19 13:08 ` Stefan Monnier
2021-08-19 15:31 ` Philip Kaludercic
2021-08-20 21:49 ` Stefan Monnier
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=875yw1u6su.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).