From: Kevin Daudt <me@ikke.info>
To: Taylor Blau <me@ttaylorr.com>
Cc: "Jeff King" <peff@peff.net>,
"Michal Suchánek" <msuchanek@suse.de>,
"Jonathan Nieder" <jrnieder@gmail.com>,
"Emily Shaffer" <emilyshaffer@google.com>,
"Git List" <git@vger.kernel.org>, "Jan Krüger" <jk@jk.gs>
Subject: Re: Should we do something with #git-devel on Freenode?
Date: Wed, 26 May 2021 22:01:02 +0200 [thread overview]
Message-ID: <YK6o/j7P0JIGW0Q0@alpha> (raw)
In-Reply-To: <YK6XvmrtrdkJvsnI@nand.local>
On Wed, May 26, 2021 at 02:47:26PM -0400, Taylor Blau wrote:
> On Thu, May 20, 2021 at 01:19:02PM -0400, Jeff King wrote:
> > So if there is a critical mass of useful people that will hang out on
> > the Matrix equivalent of #git (or whatever other tool), then that may
> > become a new place. And people who want to do that should let people
> > know where they can be found (whatever happens, I'd appreciate a PR to
> > https://github.com/git/git-scm.com updating the "Community" page).
>
> Emily tweeted today [1] that the #git channel on Freenode has been taken
> over (presumably for violating their guideline that channels not mention
> Libera in their description).
>
> So using Libera seems like a good idea (although I agree that there is
> no "official" place to go, and this is more about making people aware of
> the new status-quo). In that case, here's a PR to update the "Community"
> page on git-scm.com:
>
> https://github.com/git/git-scm.com/pull/1607
>
> Thanks,
> Taylor
>
> [1]: https://twitter.com/nasamuffin/status/1397619871278530560
We still manage #git, but #git-devel has been deowned and redirected to
##git-devel.
In the mean time, the ircops on libera helped us to register #git there
pending the official namespace registration from Junio (they have a
backlog, so they are working through that).
next prev parent reply other threads:[~2021-05-26 20:01 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-19 17:47 Should we do something with #git-devel on Freenode? Emily Shaffer
2021-05-19 19:08 ` Jonathan Nieder
2021-05-19 23:22 ` Junio C Hamano
2021-05-20 7:11 ` Michal Suchánek
2021-05-20 17:19 ` Jeff King
2021-05-20 18:08 ` Emily Shaffer
2021-05-20 21:20 ` Junio C Hamano
2021-05-21 11:19 ` Kevin Daudt
2021-07-02 12:15 ` Ævar Arnfjörð Bjarmason
2021-07-02 15:23 ` Junio C Hamano
2021-05-21 18:38 ` Felipe Contreras
2021-05-21 20:12 ` Randall S. Becker
2021-05-26 23:35 ` Ævar Arnfjörð Bjarmason
2021-05-26 23:59 ` Felipe Contreras
2021-05-27 0:24 ` Đoàn Trần Công Danh
2021-05-26 18:47 ` Taylor Blau
2021-05-26 20:01 ` Kevin Daudt [this message]
2021-05-27 17:18 ` Jan Krüger
2021-05-27 21:54 ` Ævar Arnfjörð Bjarmason
2021-05-28 1:26 ` Felipe Contreras
2021-05-28 1:36 ` Taylor Blau
2021-05-28 3:29 ` Felipe Contreras
2021-05-28 8:00 ` Jan Krüger
2021-05-28 14:37 ` Phillip Susi
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=YK6o/j7P0JIGW0Q0@alpha \
--to=me@ikke.info \
--cc=emilyshaffer@google.com \
--cc=git@vger.kernel.org \
--cc=jk@jk.gs \
--cc=jrnieder@gmail.com \
--cc=me@ttaylorr.com \
--cc=msuchanek@suse.de \
--cc=peff@peff.net \
/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.