git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Git mirror at gitlab

From
Olliver Schinagl <oliver@schinagl.nl>
Date
Mar 21, 2024, 22:27 UTC
Message-ID
<E5C00398-536B-4CE5-AB25-FE7FCD55CCD8@schinagl.nl>
In-Reply-To
<xmqqy1aba6i6.fsf@gitster.g>
Hey all,
On March 21, 2024 5:34:25 p.m. GMT+01:00, Junio C Hamano <gitster@pobox.com> wrote:
Show 9 quoted lines
>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.
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.
Olliver
Show 24 quoted lines
>> I still have not been able to reach Ævar until now. Unless somebody else
>> has a way to contact him directly we at GitLab are wondering how to
>> continue.
>
>Git @ SFC has heard from avarab@gmail.com on Nov 29, 2023 but I do
>not recall any more recent communications X-<.
>
>> It would certainly be great to set up ownership of whatever solution we
>> arrive at such that it's more distributed across the community so that
>> we don't have a single point of failure in the future. Also, I don't
>> want us at GitLab to be the sole owners of the mirror, so I have been
>> wondering how the other mirrors are set up and whom we should add to any
>> such mirror.
>
>Distribution, yes.  I do not think we mind if the set of volunteer
>owners end up to be all GitLab folks, but aiming for diversity is
>good.
>
>> In any case, once things are arranged I will collaborate with our
>> support folks to get free CI minutes for the new mirror.
>
>Wonderful.
>
>Thanks.
Previous: Junio C HamanoNext: Patrick Steinhardt
Message 9 of 23 in “Git mirror at gitlab”
  1. Olliver SchinaglDec 21, 2023
  2. Patrick SteinhardtDec 21, 2023
  3. Olliver SchinaglDec 22, 2023
  4. Patrick SteinhardtDec 28, 2023
  5. Phillip WoodDec 28, 2023
  6. Patrick SteinhardtJan 17, 2024
  7. Patrick SteinhardtMar 21, 2024
  8. Junio C HamanoMar 21, 2024
  9. Olliver SchinaglMar 21, 2024
  10. Patrick SteinhardtMar 22, 2024
  11. Christian CouderMar 22, 2024
  12. Patrick SteinhardtMar 22, 2024
  13. 1/2 cook: switch unmaintained GitLab mirror to new URLPatrick Steinhardt, Mar 29, 2024
  14. Junio C HamanoMar 29, 2024
  15. 2/2 cook: update mirror URLs to use HTTPSPatrick Steinhardt, Mar 29, 2024
  16. Olliver SchinaglMar 30, 2024
  17. Patrick SteinhardtMar 30, 2024
  18. Olliver SchinaglMar 30, 2024
  19. Patrick SteinhardtMar 30, 2024
  20. Olliver SchinaglMar 30, 2024
  21. Patrick SteinhardtMar 30, 2024
  22. Olliver SchinaglMar 30, 2024
  23. Patrick SteinhardtMar 31, 2024

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.