From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.3 (2019-12-06) on atuin.qyliss.net X-Spam-Level: X-Spam-Status: No, score=-1.1 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE autolearn=unavailable autolearn_force=no version=3.4.3 Received: by atuin.qyliss.net (Postfix, from userid 496) id 04B9210428; Sat, 15 Aug 2020 13:15:28 +0000 (UTC) Received: from [127.0.0.1] (localhost [IPv6:::1]) by atuin.qyliss.net (Postfix) with ESMTP id 6D39D10382; Sat, 15 Aug 2020 13:15:22 +0000 (UTC) Received: by atuin.qyliss.net (Postfix, from userid 496) id 0011B1037D; Sat, 15 Aug 2020 13:15:19 +0000 (UTC) Received: from mail.xndr.de (mail.xndr.de [176.9.45.248]) by atuin.qyliss.net (Postfix) with ESMTPS id 236741037C for ; Sat, 15 Aug 2020 13:15:16 +0000 (UTC) References: <874kp99m8v.fsf@xndr.de> <877du5owz2.fsf@alyssa.is> <871rkcalwh.fsf@xndr.de> <87wo247zu7.fsf@alyssa.is> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=xndr.de; s=mail; t=1597497313; bh=EMTce5BjoLO026Q0IhrnbNthrRGeBTW/YHCGFu/V8qo=; h=References:From:To:Cc:Subject:In-reply-to:Date; b=EhGsI/zQqdIJR8+CKuaQShm+0SUUvwUMCtGm8dihrYV3hKacp5e4e3TVllQqu27rf M+wcvnMP5MS+Umzlsl0xytHEA0tYPTRfqqyHAuegvqLzMAiEQnDZQ4Yln6wqZroF4q jDL06h78FXGVX2F/8DdDibXb+eBxaeWtt3kCRCyY= From: Philipp =?utf-8?Q?Steinpa=C3=9F?= To: Alyssa Ross Subject: Re: [PATCH www v2] Add and clarify matrix workarounds. In-reply-to: <87wo247zu7.fsf@alyssa.is> Date: Sat, 15 Aug 2020 15:15:09 +0200 Message-ID: <87d03sgiea.fsf@xndr.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Message-ID-Hash: SWTPZOPP7OZVOLL346SPRYQ6PMAEJBUI X-Message-ID-Hash: SWTPZOPP7OZVOLL346SPRYQ6PMAEJBUI X-MailFrom: philipp@xndr.de X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-config-1; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; suspicious-header CC: devel@spectrum-os.org X-Mailman-Version: 3.3.1 Precedence: list List-Id: Patches and low-level development discussion Archived-At: List-Archive: List-Help: List-Post: List-Subscribe: List-Unsubscribe: Added alternative matrix workarounds and streamlined the existing one. --- participating.html | 19 ++++++++++++------- 1 file changed, 12 insertions(+), 7 deletions(-) diff --git a/participating.html b/participating.html index 811fcf4..10665ca 100644 --- a/participating.html +++ b/participating.html @@ -78,13 +78,18 @@ the web.

Note for Matrix users

=20

-There appears to be an issue with Matrix's IRC bridge that prevents -Matrix users from joining #spectrum. The workaround is as follows: - -

    -
  1. Post !join #spectrum in your "Freenode IRC Bridge" chat.
    2. -
  2. Accept the invitation you are sent.
    3. -
+There appears to be an issue with Matrix's IRC bridged room that prevents +Matrix users from joining the channel with the normal alias +#freenode_#spectrum:matrix.org. There are the following workarounds: + +
    +
  • Join the room via it's internal name: + /join !ZsIiqZmCTSWHpTQWaw:matrix.org. +
  • Join the room via + matrix.= to link.
    • +
  • Ask the bridges appservice to invite you to the room: + /msg @appservice-irc:matrix.org !join #spectrum and accept = the invite. +
=20

If you experience this issue, kindly report it to the people who run -- Okay, I hope I did everything right this time :-) Thanks for your tipps Alyssa Ross writes: > Philipp Steinpa=C3=9F writes: > >> Thank you for the remarks, they were all very helpfull. >> If you want to include me in the copyright, you are free to use my full >> name. It's in the mail header now. > > Cool, so I'll add the following if that's okay: > > > >> P.S. Please feel free to comment on any potential problems with the >> formatting of these patch mails, if you want to. It's my first time >> using git via mail and I'd like todo it the proper way right away. > > Okay! Well, what you've done here has pretty much worked, but there's a > couple of things that were a little unusual: > > - When I apply a patch with git am, it expects to find the commit > message at the start of the email. So usually, when you're sending v2 > of a patch, you repeat the message from v1, because that's usually > what makes sense to be recorded in the commit log. If you want to > include stuff like you did here, describing what's changed in this > version of the patch, you can include that after the "---" (above the > diffstat), and it won't become part of the commit message. > > - Often people indicate which version of a patch they're sending using > the subject, like "[PATCH v2] Add and clarify Matrix workarounds". > > Thanks for your patch! I appreciate it -- I know it's not easy getting > up to speed with a new workflow.