help / color / mirror / code / Atom feed
From: "Daniel Shahaf" <d.s@daniel.shahaf.name>
To: devs <zsh-workers@zsh.org>
Subject: Re: gitlab out of sync with sourceforge and github repositories
Date: Sat, 17 Dec 2022 20:14:26 +0000	[thread overview]
Message-ID: <1101bc13-f451-4745-8cfb-6bfebdb684d5@app.fastmail.com> (raw)
In-Reply-To: <CAH+w=7byVWL3wdX4BJ1adJNt18VFHLd_O1Od6JTrOGPPnhyKWw@mail.gmail.com>

Bart Schaefer wrote on Sat, 17 Dec 2022 19:57 +00:00:
> On Fri, Dec 16, 2022 at 1:05 PM Jim <linux.tech.guy@gmail.com> wrote:
>> github
>> zsh-5.9-91-g1de8baded
>> gitlab
>> zsh-5.9-85-g67d4bf5bb
>> sourceforge
>> zsh-5.9-91-g1de8baded
> I think this is because Oliver and/or Daniel is/are manually updating
> gitlab, so its always going to be one attention-span behind.

Not me.  Oliver?

> On Thu, Dec 15, 2022 at 1:26 PM Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
>> Actually, I do wonder why we don't use GitLab's built-in mirroring
>> thing.  Perhaps in order to allow people to submit completion patches to
>> either GitHub or GitLab at their choice?
> How would where the patches are submitted affect this?  We're always
> going to apply them back on the sourceforge origin.  Conflicting
> patches for the same completion?

I'm not worried about conflicting patches; that possibility comes
with the territory.

Rather, I was wondering whether "make <this> GL repository a mirror of
<this> GH repository" might delete GL heads corresponding to merge
requests (MRs), since they don't exist on the GH end being pulled from.
(Cf. rsync's --delete option)

Now, I'm not even sure whether the lag observed this week was a one-time
thing or not.  However, should we determine that the GitLab mirror's
settings need to be changed, Oliver and I can effect such changes.



  reply	other threads:[~2022-12-17 20:15 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 [this message]
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

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1101bc13-f451-4745-8cfb-6bfebdb684d5@app.fastmail.com \
    --to=d.s@daniel.shahaf.name \
    --cc=zsh-workers@zsh.org \


* 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).