If I recall correctly, when the Jenkins project migrated all its repositories
from SVN to Git, the repositories were a) made read-only, b) emptied and its
content replaced by a README file with the link to the new repo and, after some
time, c) deleted.
Bruno
From: Jan Matèrne (jhm) <apa...@materne.de>
To: 'Commons Developers List' <dev@commons.apache.org>
Sent: Saturday, May 9, 2015 10:37 PM
Subject: AW: [Git] drop SVN repos for components using Git?
> > > > Do the Git repos include the Subversion commit history?
> > >
> > > Yes, it includes the full history, including tags.
> > >
> >
> > Seems reasonable to drop then.
> >
>
> hm, the problem may be, that the scm section of the poms in the pre-git
> releases point to the svn location.
We could make the svn repo read only and decide dropping later (in 2-3 years ;)
Maybe we could get statistics about how often these read-only repos are really
accessed.
Jan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
