From: Patrick Steinhardt <ps@pks.im>
To: Olliver Schinagl <oliver@schinagl.nl>
Cc: "Junio C Hamano" <gitster@pobox.com>,
git@vger.kernel.org, "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
psteinhardt@gitlab.com,
"Christian Couder" <christian.couder@gmail.com>,
"Taylor Blau" <me@ttaylorr.com>
Subject: Re: Git mirror at gitlab
Date: Fri, 22 Mar 2024 01:44:31 +0100 [thread overview]
Message-ID: <ZfzUb9HkZLq1UIed@tanuki> (raw)
In-Reply-To: <E5C00398-536B-4CE5-AB25-FE7FCD55CCD8@schinagl.nl>
[-- Attachment #1: Type: text/plain, Size: 2187 bytes --]
On Thu, Mar 21, 2024 at 11:27:07PM +0100, Olliver Schinagl wrote:
> Hey all,
>
> On March 21, 2024 5:34:25 p.m. GMT+01:00, Junio C Hamano <gitster@pobox.com> wrote:
> >Patrick Steinhardt <ps@pks.im> writes:
> >
> >>> Circling back on this topic: https://gitlab.com/git is unfortunately
> >>> taken, so it's out of question. I'd say the most pragmatic thing to do
> >>> would thus be to retain the already-existing location of the official
> >>> mirror at GitLab.
> >
> >https://gitlab.com/git/ sems to give us 404, though.
> >
>
> That seems tot indicatie this is a user, not a group (gitlab is more
> advanced then github), but I could be wrong. In both cases the user
> has set this to private.
>
> My guess is, someone set this up as a bot-user or something the like.
> Maybebgitlab could check activity (internally and confidentially) and
> see if the user would want to talk. But I admit is a bit hostile.
> Other we have no way of reaching out.
I checked with support folks and it is a private group if I remember
correctly. Whatever it was, it's not available right now.
> As for my mirror, I started my mail with I'd me more then happy to
> transfer ownership. The name I post cked as a reference to
> git-scm.org, and never intended to keep it for myself. As I initially
> wrote, I was just slow and lazy to sort thongs out ;)
>
> I will transfer and relinquish any and all control of the group once I
> know to whom.
Okay, thanks, I didn't quite remember :) In any case, unless we get a
hold of git-vcs/git, we have two viable options:
- gitvcs/git owned by Olliver.
- git-scm/git. I just discovered a few hours ago that the git-scm
group is owned by Chris, so we can set this one up easily.
I'd personally rather go with the latter, mostly because it matches our
git-scm.com domain. I also like it better than the current git-vcs/git
because of that.
So Chris, would you mind adding me (@pks-t, my non-GitLab handle) as an
additional owner of that group? I'd be happy to manage the rest from
there -- setup of the project, mirroring, CI system and changing our
docs to point to the new mirror.
Patrick
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-03-22 0:44 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 11:30 Git mirror at gitlab Olliver Schinagl
2023-12-21 11:48 ` Patrick Steinhardt
2023-12-22 14:06 ` Olliver Schinagl
2023-12-28 11:13 ` Patrick Steinhardt
2023-12-28 14:50 ` Phillip Wood
2024-01-17 6:35 ` Patrick Steinhardt
2024-03-21 11:24 ` Patrick Steinhardt
2024-03-21 16:34 ` Junio C Hamano
2024-03-21 22:27 ` Olliver Schinagl
2024-03-22 0:44 ` Patrick Steinhardt [this message]
2024-03-22 10:08 ` Christian Couder
2024-03-22 13:04 ` Patrick Steinhardt
2024-03-29 14:47 ` [PATCH 1/2] cook: switch unmaintained GitLab mirror to new URL Patrick Steinhardt
2024-03-29 18:11 ` Junio C Hamano
2024-03-29 14:47 ` [PATCH 2/2] cook: update mirror URLs to use HTTPS Patrick Steinhardt
2024-03-30 8:14 ` Git mirror at gitlab Olliver Schinagl
2024-03-30 8:18 ` Patrick Steinhardt
2024-03-30 8:20 ` Olliver Schinagl
2024-03-30 9:06 ` Patrick Steinhardt
2024-03-30 10:59 ` Olliver Schinagl
2024-03-30 18:06 ` Patrick Steinhardt
2024-03-30 23:54 ` Olliver Schinagl
2024-03-31 7:26 ` Patrick Steinhardt
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=ZfzUb9HkZLq1UIed@tanuki \
--to=ps@pks.im \
--cc=avarab@gmail.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=me@ttaylorr.com \
--cc=oliver@schinagl.nl \
--cc=psteinhardt@gitlab.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.