From: bo0od <bo0od@riseup.net>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: 48793@debbugs.gnu.org
Subject: bug#48793: Make guix room available over matrix
Date: Wed, 2 Jun 2021 21:39:26 +0000 [thread overview]
Message-ID: <a84bed4c-a926-94cd-6790-7bbde70a28c4@riseup.net> (raw)
In-Reply-To: <87tumgm2h3.fsf@nckx>
> The #guix channel is already bridged over Matrix. Is there a bug in the
> bridge? It's better to report that directly to Libera.
Im not sure im following, Does guix has its own room over matrix or not?
if yes what is it if not thats why i opened this ticket.
> Otherwise, this sounds like it belongs in the existing thread on
> guix-devel@ where everyone can suggest and discuss their favourite
> protocol, not on the Guix bug tracker.
ah i see, didnt know that i should close this and report there or
continue here ?
Tobias Geerinckx-Rice:
> Hi bo0od,
>
> The #guix channel is already bridged over Matrix. Is there a bug in the
> bridge? It's better to report that directly to Libera.
>
> Otherwise, this sounds like it belongs in the existing thread on
> guix-devel@ where everyone can suggest and discuss their favourite
> protocol, not on the Guix bug tracker.
>
> Kind regards,
>
> T G-R
next prev parent reply other threads:[~2021-06-02 21:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-02 18:42 bug#48793: Make guix room available over matrix bo0od
2021-06-02 20:22 ` Julien Lepiller
2021-06-02 21:46 ` bo0od
2021-06-02 21:50 ` Julien Lepiller
2021-06-02 21:57 ` bo0od
2021-06-03 15:34 ` Bone Baboon via Bug reports for GNU Guix
2021-06-03 19:52 ` bo0od
2021-06-02 20:32 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2021-06-02 21:39 ` bo0od [this message]
2021-06-02 22:20 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2021-06-03 19:39 ` bo0od
2021-06-03 21:18 ` Julien Lepiller
2021-06-07 22:35 ` bo0od
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a84bed4c-a926-94cd-6790-7bbde70a28c4@riseup.net \
--to=bo0od@riseup.net \
--cc=48793@debbugs.gnu.org \
--cc=me@tobias.gr \
/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/guix.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).