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: Fri, 16 Dec 2022 15:04:27 -0600	[thread overview]
Message-ID: <CA+rB6GL8yu8G+qt6tqtKx8-KvM7B54kErFL2mQhfc4Stvo+czQ@mail.gmail.com> (raw)
In-Reply-To: <20221215212612.GC8411@tarpaulin.shahaf.local2>

[-- Attachment #1.1: Type: text/plain, Size: 1489 bytes --]

Hi again,

I'm beginning to sound like a broken record. That's what happens when I try
doing things after getting a flu and covid shots(side effects: fever -
chills -
aches - sleepy). Way better than the flu or covid.  :-)

Anyway, to test, started a new terminal and shell and ran the attached
The function clones all three repositories in the /tmp directory.
The results are as follows:

URL: https://github.com/zsh-users/zsh.git
LogFileName: /tmp/zsh_git_repos/github/clone_error_log
return code:  0


URL: https://gitlab.com/zsh-org/zsh.git
LogFileName: /tmp/zsh_git_repos/gitlab/clone_error_log
return code:  0


URL: git://git.code.sf.net/p/zsh/code
LogFileName: /tmp/zsh_git_repos/sourceforge/clone_error_log
return code:  0


As you can see from the output of the git describe command, gitlab does not
the same result as the other sites.

git log starts with:

commit 67d4bf5bb936a5b95160410b4790f2bf4113c75f (HEAD -> master,
origin/master, origin/HEAD)
Author: Peter Stephenson <p.stephenson@samsung.com>
Date:   Mon Dec 12 10:30:13 2022 +0000

    51134: ! return doesn't change the return status

So unless I'm missing something, or still suffering the side effects of the
flu and
covid shots, it appears to indicate that gitlab isn't up to date.

I would appreciate it if someone could run the function and verify if they
get the
same results.

Thanks and Regards,


[-- Attachment #1.2: Type: text/html, Size: 2152 bytes --]

[-- Attachment #2: clone_zsh_repos --]
[-- Type: application/octet-stream, Size: 797 bytes --]

clone_zsh_repos () {
  emulate -L zsh
  setopt extendedglob
  local     E N P R RDN V
  local -a  D Rs URLs
  D=( '' '' zsh )
  Rs=(github/ gitlab/ sourceforge/)
  [[ ! -d $P$RDN ]] && mkdir $P$RDN
  for N ({1..${#Rs}}) {
    print '\n'${Rs[N]%/}
    [[ ! -d $P$RDN$Rs[N] ]] && mkdir $P$RDN$Rs[N]
    cd $P$RDN$Rs[N]
    print URL: $URLs[N]'\n'LogFileName: $P$RDN${Rs[N]}clone_error_log
    git clone $URLs[N] $D[N] 2>$P$RDN${Rs[N]}clone_error_log
    E=$? ; cd $OLDPWD ; print "return code:  $E"
    [[ $E -eq 0 ]] && { print ; cd $P$RDN$Rs[N]zsh && git describe ; cd $OLDPWD }
  # vim : ts=2 sw=2 sts=2 sta ai et ft=zsh :

  reply	other threads:[~2022-12-16 21:04 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 [this message]
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+rB6GL8yu8G+qt6tqtKx8-KvM7B54kErFL2mQhfc4Stvo+czQ@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).