From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Aleksandr Vityazev <avityazev@posteo.org>
Cc: Alexander Adolf <alexander.adolf@condition-alpha.com>,
emacs-devel@gnu.org
Subject: Re: [ELPA] New package: srht
Date: Wed, 18 May 2022 08:49:15 -0400 [thread overview]
Message-ID: <jwv5ym357rj.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87h75okyds.fsf@posteo.org> (Aleksandr Vityazev's message of "Tue, 17 May 2022 14:49:19 +0000")
> No, it's not. According to the documentation, forge already supports the
> sourcehut git service. Also forge and magit are not included to ELPA
> packages.
FWIW, Magit is included in NonGNU ELPA and GNU ELPA packages are allowed
to depend on NonGNU ELPA packages (it's not encouraged, admittedly).
I don't know anything about Forge so I don't know if it could be added
to NonGNU ELPA.
Besides, if "integrating with Magit or Forge" doesn't mean depending on
them, but just hooking into (or using) them if/when available, then it
can be done regardless whether they're in (Non)GNU ELPA or not.
Stefan
next prev parent reply other threads:[~2022-05-18 12:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-16 16:15 [ELPA] New package: srht Aleksandr Vityazev
2022-05-17 12:54 ` Alexander Adolf
2022-05-17 14:49 ` Aleksandr Vityazev
2022-05-18 11:15 ` Alexander Adolf
2022-05-18 12:49 ` Stefan Monnier [this message]
2022-05-18 13:13 ` Tassilo Horn
2022-05-17 16:03 ` Tassilo Horn
2022-05-17 18:42 ` Stefan Monnier
2022-05-17 19:07 ` Aleksandr Vityazev
2022-05-17 19:17 ` Stefan Monnier
2022-05-18 17:47 ` Aleksandr Vityazev
2022-05-19 4:56 ` Tassilo Horn
2022-05-19 19:10 ` Aleksandr Vityazev
2022-05-19 19:50 ` Tassilo Horn
2022-05-19 21:06 ` Aleksandr Vityazev
2022-05-20 6:05 ` Tassilo Horn
2022-05-20 18:39 ` Aleksandr Vityazev
2022-05-20 19:08 ` Stefan Kangas
2022-05-21 22:30 ` Jonas Bernoulli
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=jwv5ym357rj.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=alexander.adolf@condition-alpha.com \
--cc=avityazev@posteo.org \
--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).