Zsh Mailing List Archive
Messages sorted by: Reverse Date, Date, Thread, Author

Re: Repository/mirrors question





On Sat, Jan 22, 2022 at 1:24 PM Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx> wrote:
On Sat, Jan 22, 2022 at 11:16 AM Jim <linux.tech.guy@xxxxxxxxx> wrote:
>
> Building a new system and cloned the git repository and(for whatever reason) one of
> the mirrors(github).  I noticed  the size of the two was over 15M difference.

I think the difference is in the number of forks.  There are 341 forks
of the mirror on github and only 4 on the SourceForge original.

Aren't forks just copies of the git repository, once forked then the fork does
their own thing. That wouldn't change the repository that the fork was taken
from, would it?  'man git' hasn't any references to forks. But it wouldn't be
the first time I was wrong. What would concern me more is the object count
on gitlab's mirror.

git count-objects -v -H  ( Take prior to Sunday's commits )
sourceforge: in-pack: 98608  size-pack: 19.53 MiB
github: in-pack: 98608   size-pack: 36.25 MiB
gitlab:  in-pack: 98494  size-pack: 21.13 MiB

After Sunday's commits, I did an object comparison between sourceforce's
repository and the two mirrors.  Ignoring the size difference, the objects in
the github mirror match those in sourceforge.  But there are differences
between the gitlab mirror and sourceforge.  There are 124 objects in
sourceforge that are not in the gitlab mirror. But more surprising there are
10 objects in the gitlab mirror that are not in sourceforge.

Find differences in attachments.

Again, I don't know if this is an integrity issue or not.  I'll leave that
for someone else to determine. I do believe it should be brought to
someone's attention in case it is a problem.

I appreciate your time,

Jim

Attachment: diff_gl_sf
Description: Binary data

Attachment: diff_sf_gl
Description: Binary data



Messages sorted by: Reverse Date, Date, Thread, Author