From: Jim <email@example.com>
To: devs <firstname.lastname@example.org>
Subject: Re: gitlab out of sync with sourceforge and github repositories
Date: Mon, 6 Mar 2023 07:42:59 -0600 [thread overview]
Message-ID: <CA+rB6GLyJpPRneA8ZPKcMDTEVOW6-nBRS2PKH5zMeWCYLdDuQQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1425 bytes --]
On Sun, Dec 18, 2022 at 5:40 PM Oliver Kiddle <email@example.com> wrote:
> "Daniel Shahaf" wrote:
> > I'm not sure what does the pushes. It doesn't seem to be documented in
> > the infra repository either. Oliver, any idea why gitlab hasn't updated
> in 4.5 days?
> It was configured so as to happen automatically. Looking now, under
> Settings→Repository→Mirroring repositories, everything appears blank and
> the only Mirror direction offered appears to be "Push". Documentation
> also appears to mention that pulling is an Ultimate only feature. It may
> have only stopped now because you logged in.
> There is a programme to allow open source projects to apply for that for
> free, see: https://about.gitlab.com/solutions/open-source/join/
> However, I'm more inclined to delete the (now broken) mirror than jump
> through their hoops.
> I only ever fetched from it to get at the merge requests. A slight lag
> is not something I'd ever be especially concerned about. There have only
> been 16 merge requests. If we just want the extra backup, there are
> other options like codeberg and bitbucket.
Just wondering if there has been any decision made about the gitlab
AFAICT it hasn't updated for allmost three months.
github and sourceforge: zsh-5.9-160-g9bd9693fd
Again, just curious.
[-- Attachment #2: Type: text/html, Size: 2061 bytes --]
prev parent reply other threads:[~2023-03-06 13:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 13:47 Jim
2022-12-15 19:01 ` Jim
2022-12-15 21:26 ` Daniel Shahaf
2022-12-16 21:04 ` Jim
2022-12-17 19:57 ` Bart Schaefer
2022-12-17 20:14 ` Daniel Shahaf
2022-12-18 1:58 ` Jim
2022-12-18 19:42 ` Daniel Shahaf
2022-12-18 23:40 ` Oliver Kiddle
2023-03-06 13:42 ` Jim [this message]
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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.
Code repositories for project(s) associated with this public inbox
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).