From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Oliver Smith <ollieparanoid@postmarketos.org>
Cc: tools@linux.kernel.org
Subject: Re: [PATCH b4 0/1] How about adding SourceHut lists as 2nd backend?
Date: Mon, 14 Nov 2022 09:49:11 -0500 [thread overview]
Message-ID: <20221114144911.jdvdjkqi6mkzjtv6@meerkat.local> (raw)
In-Reply-To: <20221112131114.2370-1-ollieparanoid@postmarketos.org>
On Sat, Nov 12, 2022 at 02:11:13PM +0100, Oliver Smith wrote:
> Hi,
>
> I found that with relatively few changes it's possible to add SourceHut
> as alternative backend to b4. Is this desirable to have in b4?
Absolutely, I am all for making b4 work with sourcehut. I haven't yet had a
chance to review your patch, but I hope to be able to work on it today or
tomorrow. Some features will require rethinking for sure (e.g. we assume we're
always talking to a public-inbox instance, so when it's not the case we'll
have to adjust features like querying the remote for updates based on
change-id).
Cheers,
-K
prev parent reply other threads:[~2022-11-14 14:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-12 13:11 [PATCH b4 0/1] How about adding SourceHut lists as 2nd backend? Oliver Smith
2022-11-12 13:11 ` [PATCH b4 1/1] RFC: Support SourceHut as additional backend Oliver Smith
2022-11-14 14:49 ` Konstantin Ryabitsev [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221114144911.jdvdjkqi6mkzjtv6@meerkat.local \
--to=konstantin@linuxfoundation.org \
--cc=ollieparanoid@postmarketos.org \
--cc=tools@linux.kernel.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.
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).