help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: linuxtechguy@gmail.com
Cc: devs <zsh-workers@zsh.org>
Subject: Re: gitlab out of sync with sourceforge and github repositories
Date: Sat, 17 Dec 2022 11:57:57 -0800	[thread overview]
Message-ID: <CAH+w=7byVWL3wdX4BJ1adJNt18VFHLd_O1Od6JTrOGPPnhyKWw@mail.gmail.com> (raw)
In-Reply-To: <CA+rB6GL8yu8G+qt6tqtKx8-KvM7B54kErFL2mQhfc4Stvo+czQ@mail.gmail.com>

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.

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?

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

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='CAH+w=7byVWL3wdX4BJ1adJNt18VFHLd_O1Od6JTrOGPPnhyKWw@mail.gmail.com' \
    --to=schaefer@brasslantern.com \
    --cc=linuxtechguy@gmail.com \
    --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).