commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bruno P. Kinoshita" <>
Subject Re: AW: [Git] drop SVN repos for components using Git?
Date Sat, 09 May 2015 10:40:14 GMT
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.

      From: Jan Matèrne (jhm) <>
 To: 'Commons Developers List' <> 
 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.


To unsubscribe, e-mail:
For additional commands, e-mail:


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message