From: Alaa Mohamed <eng.alaamohamedsoliman.am@gmail.com>
To: brunodout.dev@gmail.com, Stefano Brivio <sbrivio@redhat.com>
Cc: outreachy@lists.linux.dev
Subject: Re: IRC channels
Date: Mon, 28 Mar 2022 17:58:00 +0200 [thread overview]
Message-ID: <1d305abf-1b0d-c43e-6fe9-aa6e74fcb430@gmail.com> (raw)
In-Reply-To: <dd79b324e01740af619f4d3e0a57e1409e718606.camel@gmail.com>
On ٢٨/٣/٢٠٢٢ ٠٢:١٦, brunodout.dev@gmail.com wrote:
> Hi Alaa,
> Hi Stefano,
>
> On Sun, 2022-03-27 at 21:30 +0200, Stefano Brivio wrote:
>> Hi Alaa,
>>
>> On Sun, 27 Mar 2022 20:08:01 +0200
>> Alaa Mohamed <eng.alaamohamedsoliman.am@gmail.com> wrote:
>>
>>> Hello All,
>>>
>>> I am Alaa , My initial application approved. I have
> Heyy Alaa, congratulations for that! I am very glad to be
> here and hope you are too!
>
>>> I couldn’t join both irc channels, any guide plz
> Are you using the web client? If you are, you might access
> one of Stefano's links to join the first channel, and then
> join the second one with the command:
>
> /join #second-channel
>
>> Can you try these links?
>>
>>
>> https://webchat.oftc.net/?randomnick=1&channels=outreachy-
>> kernel-networking&prompt=1
>>
>>
>> https://webchat.oftc.net/?randomnick=1&channels=kernel-
>> outreachy&prompt=1
> Using both links as Stefano said will also work, but you'll
> have two browser tabs and two different connections using
> two different nicknames for that. I think adding both
> channels sepparated by comma in the channels=... part of the
> URL might also work, but I haven't tried.
>
> Best regards,
> Bruno (IRC: CodeAgain)
Hi Stefano & Bruno
Thanks a lot for your help , I am able to join both channels.
Best Regards,
Alaa
prev parent reply other threads:[~2022-03-28 15:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-27 18:08 IRC channels Alaa Mohamed
2022-03-27 19:30 ` Stefano Brivio
2022-03-28 0:16 ` brunodout.dev
2022-03-28 15:58 ` Alaa Mohamed [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=1d305abf-1b0d-c43e-6fe9-aa6e74fcb430@gmail.com \
--to=eng.alaamohamedsoliman.am@gmail.com \
--cc=brunodout.dev@gmail.com \
--cc=outreachy@lists.linux.dev \
--cc=sbrivio@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.