From: Aleksandr Vityazev <avityazev@disroot.org>
To: Philip Kaludercic <philipk@posteo.net>
Cc: emacs-devel@gnu.org, Stefan Kangas <stefankangas@gmail.com>
Subject: Re: [ELPA] New package devicetree-ts-mode
Date: Tue, 16 Jan 2024 11:08:20 +0300 [thread overview]
Message-ID: <87ttnd3dl7.fsf@disroot.org> (raw)
In-Reply-To: <87ttndg2gu.fsf@posteo.net> (Philip Kaludercic's message of "Tue, 16 Jan 2024 07:30:09 +0000")
On 2024-01-16 07:30, Philip Kaludercic wrote:
> Aleksandr Vityazev <avityazev@disroot.org> writes:
>
>> On 2024-01-16 06:18, Philip Kaludercic wrote:
>>
>>> Aleksandr Vityazev <avityazev@disroot.org> writes:
>>>
>>>> Hello,
>>>>
>>>> Since the previous thread [1] got lost over time and no more replies,
>>>> I'm starting a new one.
>>>
>>> Sorry about that, I hadn't gotten around to answering your last ping.
>>>
>>>> All of Philip's suggested points have been fixed, is there any reason
>>>> why this package should not be included in ELPA? I am willing to listen
>>>> and fix if possible.
>>>
>>> I think code-wise everything should be fine. Just to be sure, you have
>>> signed the FSF CA and are familiar with how the ELPA build server works
>>> (at least from a package developer perspective)?
>>>
>>
>> Yes, I have a signed CA FSF. One of my packages is already in ELPA, so I'm more
>> or less familiar with the build process.
>
> OK, great, I have tried building the package and it works. The package
> has been added to the archive and should appear soon enough.
>
> Another tip I can give you is that since you have a mailing list on
> Soucehut, I recommend adding that is the maintainer address in the
> package header.
Thanks, I'll add the mailing list address to the package header.
>
> Also, is it necessary to distribute both the README.md and README.org in
> the package tarball? I would assume the former is for Sourcehut,
> right?
Yes, README.md for Sourcehut. I prefer to write README in org format. It
is possible to do this by generating html from README.org and adding it
as a custom one. In this case, only README.org can be kept. Maybe I'll
switch to this method later.
At the moment I can add one of the READMEs to elpaignore if necessary.
>>>> Link to repository - https://git.sr.ht/~akagi/devicetree-ts-mode/
>>>>
>>>> [1] https://mail.gnu.org/archive/html/emacs-devel/2023-12/msg00629.html
--
Best regards,
Aleksandr Vityazev
next prev parent reply other threads:[~2024-01-16 8:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-16 0:38 [ELPA] New package devicetree-ts-mode Aleksandr Vityazev
2024-01-16 6:18 ` Philip Kaludercic
2024-01-16 6:42 ` Aleksandr Vityazev
2024-01-16 7:30 ` Philip Kaludercic
2024-01-16 8:08 ` Aleksandr Vityazev [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-21 17:47 Aleksandr Vityazev
2023-12-22 7:36 ` Philip Kaludercic
2023-12-22 20:08 ` Aleksandr Vityazev
2024-01-07 13:27 ` Aleksandr Vityazev
2023-12-22 16:02 ` Stefan Kangas
2023-12-22 20:36 ` Aleksandr Vityazev
2024-02-20 3:04 ` Björn Bidar
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=87ttnd3dl7.fsf@disroot.org \
--to=avityazev@disroot.org \
--cc=emacs-devel@gnu.org \
--cc=philipk@posteo.net \
--cc=stefankangas@gmail.com \
/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).