From: "Alex Bennée" <alex.bennee@linaro.org>
To: qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, thuth@redhat.com,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: [RFC PATCH] support.md: add a link to matrix bridge to IRC
Date: Wed, 17 Mar 2021 16:02:59 +0000 [thread overview]
Message-ID: <20210317160259.14098-1-alex.bennee@linaro.org> (raw)
We want users to be able to use newer tooling and not be stuck with
IRC like the rest of the fossils. As the #QEMU channel is bridged by
the matrix.org server lets point there as well. At least it's not
Slack.
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
---
support.md | 10 ++++++----
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/support.md b/support.md
index f6ee85c..252351c 100644
--- a/support.md
+++ b/support.md
@@ -33,10 +33,12 @@ want to send your question to another of [QEMU's mailing
lists](https://wiki.qemu.org/MailingLists)
* A lot of developers hang around on IRC (network: irc.oftc.net,
-channel #qemu).<br> QEMU developers tend to hold normal office hours
-and are distributed around the world. Please be patient as you may
-have to wait some time for a response. If you can't leave IRC open and
-wait you may be better served by a mailing list.
+channel #qemu, also available via
+[Matrix](https://matrix.to/#/#_oftc_#qemu:matrix.org)).<br> QEMU
+developers tend to hold normal office hours and are distributed around
+the world. Please be patient as you may have to wait some time for a
+response. If you can't leave IRC open and wait you may be better
+served by a mailing list.
* If you think you have found a bug you can report it on [our bug
tracker](https://bugs.launchpad.net/qemu/).<br>
--
2.20.1
next reply other threads:[~2021-03-17 16:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-17 16:02 Alex Bennée [this message]
2021-03-17 16:44 ` [RFC PATCH] support.md: add a link to matrix bridge to IRC Philippe Mathieu-Daudé
2021-03-17 16:55 ` Daniel P. Berrangé
2021-03-17 17:24 ` Paolo Bonzini
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=20210317160259.14098-1-alex.bennee@linaro.org \
--to=alex.bennee@linaro.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
/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 NNTP newsgroup(s).