You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by sebb <se...@gmail.com> on 2015/05/08 17:53:12 UTC
[Git] drop SVN repos for components using Git?
Is there any point in keeping the SVN repos for components that have
moved to Git?
They are read-only (or should be) and are not synchronised with the
Git repo, so they can be confusing.
If there is a need to keep them, they should be renamed so people
cannot accidentally use them.
It might be an idea to keep just a README file pointing to the Git
repo, but I think the contents should be dropped, or perhaps moved
under commons/Git, at least temporarily.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [Git] drop SVN repos for components using Git?
Posted by Jochen Wiedmann <jo...@gmail.com>.
On Sat, May 9, 2015 at 2:35 PM, sebb <se...@gmail.com> wrote:
> Poms cannot be changed *after* release.
No, but you can release a new one.
> There may even be some CVS references in early POMs; that does not
> mean the ASF has not migrated away from CVS.
Quite so. And I can't remember a single case where that proved to be a problem.
Jochen
--
Any world that can produce the Taj Mahal, William Shakespeare,
and Stripe toothpaste can't be all bad. (C.R. MacNamara, One Two Three)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [Git] drop SVN repos for components using Git?
Posted by sebb <se...@gmail.com>.
On 9 May 2015 at 13:17, Jochen Wiedmann <jo...@gmail.com> wrote:
> On Sat, May 9, 2015 at 12:14 PM, Benedikt Ritter <br...@apache.org> wrote:
>> hm, the problem may be, that the scm section of the poms in the pre-git
>> releases point to the svn location.
>
>
> If so, then the project hasn't really migrated to git, has it?
Poms cannot be changed *after* release.
There may even be some CVS references in early POMs; that does not
mean the ASF has not migrated away from CVS.
> Jochen
>
>
> --
> Any world that can produce the Taj Mahal, William Shakespeare,
> and Stripe toothpaste can't be all bad. (C.R. MacNamara, One Two Three)
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [Git] drop SVN repos for components using Git?
Posted by Jochen Wiedmann <jo...@gmail.com>.
On Sat, May 9, 2015 at 12:14 PM, Benedikt Ritter <br...@apache.org> wrote:
> hm, the problem may be, that the scm section of the poms in the pre-git
> releases point to the svn location.
If so, then the project hasn't really migrated to git, has it?
Jochen
--
Any world that can produce the Taj Mahal, William Shakespeare,
and Stripe toothpaste can't be all bad. (C.R. MacNamara, One Two Three)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: AW: [Git] drop SVN repos for components using Git?
Posted by "Bruno P. Kinoshita" <br...@yahoo.com.br>.
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) <ap...@materne.de>
To: 'Commons Developers List' <de...@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-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
AW: [Git] drop SVN repos for components using Git?
Posted by "Jan Matèrne (jhm)" <ap...@materne.de>.
> > > > 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-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [Git] drop SVN repos for components using Git?
Posted by Benedikt Ritter <br...@apache.org>.
2015-05-08 21:55 GMT+02:00 Gary Gregory <ga...@gmail.com>:
> On Fri, May 8, 2015 at 9:02 AM, Luc Maisonobe <lu...@spaceroots.org> wrote:
>
> > Le 08/05/2015 17:55, Adrian Crum a écrit :
> > > 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.
>
> Gary
>
>
> >
> > Luc
> >
> > >
> > > Adrian Crum
> > > Sandglass Software
> > > www.sandglass-software.com
> > >
> > > On 5/8/2015 8:53 AM, sebb wrote:
> > >> Is there any point in keeping the SVN repos for components that have
> > >> moved to Git?
> > >>
> > >> They are read-only (or should be) and are not synchronised with the
> > >> Git repo, so they can be confusing.
> > >>
> > >> If there is a need to keep them, they should be renamed so people
> > >> cannot accidentally use them.
> > >>
> > >> It might be an idea to keep just a README file pointing to the Git
> > >> repo, but I think the contents should be dropped, or perhaps moved
> > >> under commons/Git, at least temporarily.
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> > >> For additional commands, e-mail: dev-help@commons.apache.org
> > >>
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> > > For additional commands, e-mail: dev-help@commons.apache.org
> > >
> > >
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> > For additional commands, e-mail: dev-help@commons.apache.org
> >
> >
>
>
> --
> E-Mail: garydgregory@gmail.com | ggregory@apache.org
> Java Persistence with Hibernate, Second Edition
> <http://www.manning.com/bauer3/>
> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
> Spring Batch in Action <http://www.manning.com/templier/>
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
>
--
http://people.apache.org/~britter/
http://www.systemoutprintln.de/
http://twitter.com/BenediktRitter
http://github.com/britter
Re: [Git] drop SVN repos for components using Git?
Posted by Gary Gregory <ga...@gmail.com>.
On Fri, May 8, 2015 at 9:02 AM, Luc Maisonobe <lu...@spaceroots.org> wrote:
> Le 08/05/2015 17:55, Adrian Crum a écrit :
> > Do the Git repos include the Subversion commit history?
>
> Yes, it includes the full history, including tags.
>
Seems reasonable to drop then.
Gary
>
> Luc
>
> >
> > Adrian Crum
> > Sandglass Software
> > www.sandglass-software.com
> >
> > On 5/8/2015 8:53 AM, sebb wrote:
> >> Is there any point in keeping the SVN repos for components that have
> >> moved to Git?
> >>
> >> They are read-only (or should be) and are not synchronised with the
> >> Git repo, so they can be confusing.
> >>
> >> If there is a need to keep them, they should be renamed so people
> >> cannot accidentally use them.
> >>
> >> It might be an idea to keep just a README file pointing to the Git
> >> repo, but I think the contents should be dropped, or perhaps moved
> >> under commons/Git, at least temporarily.
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> >> For additional commands, e-mail: dev-help@commons.apache.org
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> > For additional commands, e-mail: dev-help@commons.apache.org
> >
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
--
E-Mail: garydgregory@gmail.com | ggregory@apache.org
Java Persistence with Hibernate, Second Edition
<http://www.manning.com/bauer3/>
JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
Spring Batch in Action <http://www.manning.com/templier/>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory
Re: [Git] drop SVN repos for components using Git?
Posted by Luc Maisonobe <lu...@spaceroots.org>.
Le 08/05/2015 17:55, Adrian Crum a écrit :
> Do the Git repos include the Subversion commit history?
Yes, it includes the full history, including tags.
Luc
>
> Adrian Crum
> Sandglass Software
> www.sandglass-software.com
>
> On 5/8/2015 8:53 AM, sebb wrote:
>> Is there any point in keeping the SVN repos for components that have
>> moved to Git?
>>
>> They are read-only (or should be) and are not synchronised with the
>> Git repo, so they can be confusing.
>>
>> If there is a need to keep them, they should be renamed so people
>> cannot accidentally use them.
>>
>> It might be an idea to keep just a README file pointing to the Git
>> repo, but I think the contents should be dropped, or perhaps moved
>> under commons/Git, at least temporarily.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [Git] drop SVN repos for components using Git?
Posted by Adrian Crum <ad...@sandglass-software.com>.
Do the Git repos include the Subversion commit history?
Adrian Crum
Sandglass Software
www.sandglass-software.com
On 5/8/2015 8:53 AM, sebb wrote:
> Is there any point in keeping the SVN repos for components that have
> moved to Git?
>
> They are read-only (or should be) and are not synchronised with the
> Git repo, so they can be confusing.
>
> If there is a need to keep them, they should be renamed so people
> cannot accidentally use them.
>
> It might be an idea to keep just a README file pointing to the Git
> repo, but I think the contents should be dropped, or perhaps moved
> under commons/Git, at least temporarily.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org