[prev in list] [next in list] [prev in thread] [next in thread] 

List:       macports-users
Subject:    Re: GitHub migration complete
From:       Lawrence_Velázquez <larryv () macports ! org>
Date:       2016-10-31 19:28:03
Message-ID: 46C6D381-C34C-417D-8E6A-9CF4BB78A052 () macports ! org
[Download RAW message or body]

> On Oct 31, 2016, at 1:16 PM, Thibaut Paumard <thibaut@macports.org> wrote:
> 
> Le 31/10/2016 à 17:23, Lawrence Velázquez a écrit :
> > > On Oct 31, 2016, at 12:16 PM, Thibaut Paumard <thibaut@macports.org> wrote:
> > > 
> > > > Le 31/10/2016 à 17:01, René J.V. Bertin a écrit :
> > > > > On Monday October 31 2016 10:00:05 Ryan Schmidt wrote:
> > > > > 
> > > > > This issue only affects the very small percentage of the MacPorts user \
> > > > > population (including developers and maintainers) that clones the git \
> > > > > repository. Most users will use the rsync server, on which we do generate \
> > > > > portindexes for each macOS version.
> > > > 
> > > > Of course, but note how I used the word collective, which was supposed to \
> > > > include the idea that portindex has to be run each time by every user. :) 
> > > 
> > > I would actually believe the number of affected users should be between
> > > very small and zero.
> > 
> > Pretty much.
> > 
> > In any case, between the capabilities of Git itself and the facilities GitHub \
> > provides, I do not believe it is possible to do what you suggest.
> 
> You mean what René is suggesting?

Yes.

vq
_______________________________________________
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users


[prev in list] [next in list] [prev in thread] [next in thread]