On Sun, Mar 6, 2022 at 5:24 PM sebb <seb...@gmail.com> wrote:

> On Sun, 6 Mar 2022 at 17:57, Daniel Gruno <humbed...@apache.org> wrote:
> >
> > On 06/03/2022 18.43, sebb wrote:
> > > The GitHub repo has been forcibly changed to track
> > >
> > > https://svn.apache.org/repos/asf/steve/trunk
> > > instead of
> > > https://svn.apache.org/repos/asf/steve/trunk/pysteve
> > >
> > > This has invalidated all the forks, and broken all the PRs.
> > >
> > > That is very discouraging for contributors.
> > >
> > > Was it really necessary to do it that way, especially without applying
> > > the PRs first?
> >
> > It's an unfortunate side effect, agreed. It was not foreseen that GitHub
> > would blanket invalidate everything.
>
> I don't believe that this could not have been forseen.
> The changes had to be force-pushed, which is a normally disallowed
> precisely because of the problems it causes.
>

svn is the primary authority. The repository on github is an improper
reflection of that (it was rooted at trunk/pysteve/ rather than trunk/ )
... it was broken to begin with.

Sure, anybody using the github version has been inconvienced. All 3 of them.

Reply via email to