unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Tassilo Horn <tsdh@gnu.org>
To: Alexander Adolf <alexander.adolf@condition-alpha.com>
Cc: Aleksandr Vityazev <avityazev@posteo.org>, emacs-devel@gnu.org
Subject: Re: [ELPA] New package: srht
Date: Tue, 17 May 2022 18:03:57 +0200	[thread overview]
Message-ID: <87k0akdtim.fsf@gnu.org> (raw)
In-Reply-To: <FEEDDDEA-F7CA-4077-9528-E39D8585AC63@condition-alpha.com>

Alexander Adolf <alexander.adolf@condition-alpha.com> writes:

> 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?

I've had a brief look and the answer is no.  But I think once more sr.ht
APIs are supported by the package, it might be possible to make forge
work with sr.ht.  But even then, that won't be easy.

I think the basic problem is that with forges like GitHub/GitLab/etc,
once you know the project URL, everything else (issues, PRs, whatever)
can be derived from that.

With sr.ht, that's not the case.  There are many standalone git repos
there which have no project.  Similarly, there are trackers with no
repo.  Or projects with three repos but two trackers.  And there are no
PRs at all but patches are sent to mailinglists of which there can also
be many for one project or one for many projects.

I think the "hub" api will eventually be able to answer questions such
as "what is the issue tracker for project X" or "what is the git/hg repo
for project X" but that's not yet there.

Bye,
Tassilo



  parent reply	other threads:[~2022-05-17 16:03 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
2022-05-18 13:13       ` Tassilo Horn
2022-05-17 16:03   ` Tassilo Horn [this message]
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=87k0akdtim.fsf@gnu.org \
    --to=tsdh@gnu.org \
    --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).