Infra turns out to have a strong preference for leaving SVN 'as is'. I
got a dispensation to add a readme pointing across to git. So we might
want to plan to follow that pattern.
On Sun, Feb 15, 2015 at 12:45 AM, Hervé BOUTEMY wrote:
> perhaps adding instruction on the git migration Wiki page [1
perhaps adding instruction on the git migration Wiki page [1] would help
having easier and consistent work done on every migration
Regards,
Hervé
[1]
https://cwiki.apache.org/confluence/display/MAVEN/Git+Migration#GitMigration-KeepingtrackofauthorativeSCMforeachplugin
Le lundi 9 février 2015
I would go for a README.txt in the trunk, delete all branches and
leave the tags alone as these are referenced in the POMs.
Regards Mirko
--
http://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen)
https://bitbucket.org/mfriedenhagen/
On Mon,
Yeah, I was thinking of old braches and tags.
README sounds like a good idea.
Kristian
2015-02-09 18:12 GMT+01:00 Benson Margulies :
> On Mon, Feb 9, 2015 at 12:10 PM, Kristian Rosenvold
> wrote:
>> Just leave it as-is ?
>
>
> Surely at least a README.txt at the top to redirect?
>
>
>>
>>
>> K
On Mon, Feb 9, 2015 at 12:10 PM, Kristian Rosenvold
wrote:
> Just leave it as-is ?
Surely at least a README.txt at the top to redirect?
>
>
> Kristian
>
>
> 2015-02-09 18:08 GMT+01:00 Benson Margulies :
>> https://git-wip-us.apache.org/repos/asf/maven-archetype.git
>>
>> Momentarily it will be
Just leave it as-is ?
Kristian
2015-02-09 18:08 GMT+01:00 Benson Margulies :
> https://git-wip-us.apache.org/repos/asf/maven-archetype.git
>
> Momentarily it will be R/W and have a github mirror.
>
> I'll be making the pom scm updates.
>
> How ruthlessly do I prune svn?
>
>
https://git-wip-us.apache.org/repos/asf/maven-archetype.git
Momentarily it will be R/W and have a github mirror.
I'll be making the pom scm updates.
How ruthlessly do I prune svn?
-
To unsubscribe, e-mail: dev-unsubscr...@maven
