help / color / mirror / code / Atom feed
From: Jim <linux.tech.guy@gmail.com>
To: devs <zsh-workers@zsh.org>
Subject: Re: gitlab out of sync with sourceforge and github repositories
Date: Thu, 15 Dec 2022 13:01:57 -0600	[thread overview]
Message-ID: <CA+rB6G+2-e3M-=pL4J+sm+P9JaPn-40aGh4nu1CvczZfg-Lz4A@mail.gmail.com> (raw)
In-Reply-To: <CA+rB6G+U5_AEMrcZgNwmEYhPtmUNZjAFoiQ=Y4iuo15Q6zF=CA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1130 bytes --]

Ignore last message.  Sorry for the noise. A new clone is fine.  Started
working with
worktrees and am guessing my local repository is in some state that I
haven't figured
out yet. Something else I need to learn about git. Again, sorry for the


On Thu, Dec 15, 2022 at 7:47 AM Jim <linux.tech.guy@gmail.com> wrote:

> Hi everyone,
> Just an observation.  Since I submitted a question on the mirrors back in
> January
> I keep a copy of all 3 repositories. I manually run a script that updates
> all of them
> from time to time. What I have noticed is(at times) gitlab may take a
> couple of
> days(maybe more) to be in sync with the other two. Most of the time all
> three seem
> to stay in sync. As an example for the last couple of "my day times":
> sourceforge:  zsh-5.9-88-g6d49734d4
> github: zsh-5.9-88-g6d49734d4
> gitlab: zsh-5.9-85-g67d4bf5bb
> Don't know if this is an issue or a procedural thing. Just my observation.
> Thought I would let you know in case there may be an issue. If this is
> normal,
> sorry for the noise.
> Again, thanks to all for your work on zsh.
> Regards,
> Jim Murphy

[-- Attachment #2: Type: text/html, Size: 1722 bytes --]

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

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='CA+rB6G+2-e3M-=pL4J+sm+P9JaPn-40aGh4nu1CvczZfg-Lz4A@mail.gmail.com' \
    --to=linux.tech.guy@gmail.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).