From: Alexander Adolf <alexander.adolf@condition-alpha.com>
To: Aleksandr Vityazev <avityazev@posteo.org>
Cc: emacs-devel@gnu.org
Subject: Re: [ELPA] New package: srht
Date: Tue, 17 May 2022 14:54:41 +0200 [thread overview]
Message-ID: <FEEDDDEA-F7CA-4077-9528-E39D8585AC63@condition-alpha.com> (raw)
In-Reply-To: <87tu9p4fop.fsf@posteo.org>
[-- Attachment #1.1: Type: text/plain, Size: 775 bytes --]
Hello Aleksandr,
Just a quick question which sprang to my mind, and without having looked into the details of your package: does it integrate with magit and forge in any way?
Cheers,
--alex
--
www.condition-alpha.com / @c_alpha
Sent from my iPhone; apologies for brevity and autocorrect weirdness.
> On 16. May 2022, at 20:02, Aleksandr Vityazev <avityazev@posteo.org> wrote:
>
>
> Hello,
>
> I'd like to submit srht.el [1] to GNU ELPA. srht provides bindings to
> the Sourcehut REST API as well as commands for interacting with it. It
> currently supports two services: git.sr.ht — git hosting and paste.sr.ht
> — ad-hoc text file hosting.
>
> [1] https://git.sr.ht/~akagi/srht.el
>
> --
> Best regards,
> Aleksandr Vityazev
[-- Attachment #1.2: 0001-elpa-packages-srht-New-package.patch --]
[-- Type: application/octet-stream, Size: 948 bytes --]
From b454f08ba9b7cd0e1b9f896c670f197683c37758 Mon Sep 17 00:00:00 2001
Message-Id: <b454f08ba9b7cd0e1b9f896c670f197683c37758.1652715289.git.avityazev@posteo.org>
From: Aleksandr Vityazev <avityazev@posteo.org>
Date: Mon, 16 May 2022 15:36:21 +0300
Subject: [PATCH] * elpa-packages (srht): New package
---
elpa-packages | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/elpa-packages b/elpa-packages
index 0a72606e4c..294d95e251 100644
--- a/elpa-packages
+++ b/elpa-packages
@@ -585,6 +585,10 @@
("sql-cassandra" :url nil)
("sql-indent" :url "https://github.com/alex-hhh/emacs-sql-indent")
("sql-smie" :url nil)
+ ("srht" :url "https://git.sr.ht/~akagi/srht.el"
+ :ignored-files ("LICENSE")
+ :doc "README.org"
+ :auto-sync t)
("ssh-deploy" :url "https://github.com/cjohansson/emacs-ssh-deploy")
("stream" :url nil)
("svg" :core ("lisp/svg.el"))
--
2.36.0
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 1944 bytes --]
next prev parent reply other threads:[~2022-05-17 12:54 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 [this message]
2022-05-17 14:49 ` Aleksandr Vityazev
2022-05-18 11:15 ` Alexander Adolf
2022-05-18 12:49 ` Stefan Monnier
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=FEEDDDEA-F7CA-4077-9528-E39D8585AC63@condition-alpha.com \
--to=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).