On Sat, 25 May 2019 at 00:13, Gary Gregory wrote:
>
> I like the pointer idea.
This is an example of what we did for the original moves:
http://svn.apache.org/repos/asf/commons/proper/io/IoNowUsesGit.txt
> Gary
>
> On Fri, May 24, 2019, 18:35 sebb wrote:
>
> > On Fri, 24 May 2019 at 22:37, Emm
I like the pointer idea.
Gary
On Fri, May 24, 2019, 18:35 sebb wrote:
> On Fri, 24 May 2019 at 22:37, Emmanuel Bourg wrote:
> >
> > Le 24/05/2019 à 22:59, sebb a écrit :
> >
> > > The simplest way to stop further updates is probably to rename the SVN
> > > directory from /proper to /_moved_to_
On Fri, 24 May 2019 at 22:37, Emmanuel Bourg wrote:
>
> Le 24/05/2019 à 22:59, sebb a écrit :
>
> > The simplest way to stop further updates is probably to rename the SVN
> > directory from /proper to /_moved_to_git. This will still allow
> > updates by PMC members, but it's much more obvious that
Le 24/05/2019 à 22:59, sebb a écrit :
> The simplest way to stop further updates is probably to rename the SVN
> directory from /proper to /_moved_to_git. This will still allow
> updates by PMC members, but it's much more obvious that the SVN repo
> should no longer be updated.
Couldn't we set th
Sounds like a good plan to me.
+1
Sent from Yahoo Mail on Android
On Sat, 25 May 2019 at 9:00, sebb wrote: Some updates
have been made to the Commons 'proper' SVN repos since
they were converted to Git.
Such changes should not have been made, as they are not automatically
reflected in the
Some updates have been made to the Commons 'proper' SVN repos since
they were converted to Git.
Such changes should not have been made, as they are not automatically
reflected in the Git repos.
I think we need to do the following:
- revert the spurious changes so SVN reflects the state at conver
