Are you thinking about the svn references etched into each commit ? The current git-svn repos all have this information appended at the end of each commit: git-svn-id: https://svn.apache.org/repos/asf/maven/surefire/trunk@1374642 13f79535-47bb-0310-9956-ffa450edef68
Personally I think we should keep them, since they contain the historical reference to the SVN commit number. And technically we have a lot of jiras referencing "r990909" so removing them is not a good idea wrt traceability of changes. I know some projects (spring-framework) removed them and others kept them. But they have value for us; at least the revision number. We could consider rewriting it to just "r900900" although personally I think it's just uneccesary work. Kristian 2012/9/12 Nord, James <jn...@nds.com>: > The existing ones will likely have a lot of svn metadata which would tnhen be > broken / wrong and then could cause issues/confusion in the future > > I have migrated svn repos using the scrips at > https://github.com/nirvdrum/svn2git which tidies up this extra info and does > some extra housekeeping. > > Should you wish to split the svn structure then this allows you to do that. > > YMMV - but also something that you may not have been aware of. > > /James > >> -----Original Message----- >> From: Olivier Lamy [mailto:ol...@apache.org] >> Sent: 12 September 2012 13:26 >> To: Maven Developers List >> Subject: Re: Plan for git migration >> >> 2012/9/12 Kristian Rosenvold <kristian.rosenv...@gmail.com>: >> > Just to clarify additionally: There are existing read-only clones of a >> > lot of our projects (i'm sure infra can make the rest if they have >> > value) >> > >> > Some of these are excellent and of high quality (surefire, m3 + it's >> > are the ones I know of) while at least maven-plugins is useless (due >> > to a strange interpretation of tags - try checking out a tag in the >> > current maven-plugins git clone !!!). So we need to collect the >> > assessments of which repos are "migration ready" and which are not. >> > Any community input on this would be great! (If you've used the clone >> > and find that tags/branches etc work according to expectations we're >> > cool) >> > >> > For those that are migration ready the process is is something like this: >> > >> > 1. Have infra make the existing read-only mirror the official master. >> > 2. Change scm url in pom >> > 3. Update github mirroring url (file issue with github) >> that's something we maintain @asf infra. >> I recommend you lurking on infra@ mailing list (if you don't already) as some >> discussions will start here. (see >> http://www.apache.org/dev/infra-mail.html) >> >> > 4. Celebrate >> > >> > >> > For those that for /some/ reason are not ready, we need to resolve >> > what needs to be done. >> > >> > Kristian >> > >> > >> > >> > >> > >> > 2012/9/12 Baptiste MATHUS <m...@batmat.net>: >> >> Hi, >> >> >> >> +1. >> >> Though I'm volunteering to help, as I'm not Maven committer, I don't >> >> know if I'm really allowed to help. >> >> I could help on some projects if needed (I can see maybe enforcer & >> >> release for example). >> >> >> >> By the way, I'm not sure how this is supposed to work. After reading >> >> Kristian comment, I discovered there's actually already many (if not >> >> all) Maven projects that seem migrated (?). >> >> http://git.apache.org/ Is this something that was done by someone >> >> during the night? :-). >> >> >> >> Or maybe that repos are not correct in some way (Kristian's comment >> >> say some are already usable as-is)? >> >> >> >> What makes a repo correct or not to be used as-is? >> >> >> >> Looking at the repo structure from the HTTP interface, I'm under the >> >> impression this is a git repo created by git svn (or svn2git?), . >> >> My naive first guess understanding is that there already may be a >> >> batch of "maven git scripts" running on the infrastructure that would >> >> git-svn the main repo, then filter-branch this repo for a bunch of >> >> directories (release, enforcer, etc.). >> >> >> >> If this is so, not totally sure what would be left? >> >> >> >> Thanks. >> >> >> >> 2012/9/12 Benson Margulies <bimargul...@gmail.com> >> >> >> >>> Who is going to open the initial negotiation with INFRA? >> >>> >> >>> On Wed, Sep 12, 2012 at 4:44 AM, Olivier Lamy <ol...@apache.org> >> wrote: >> >>> > Hi Folks, >> >>> > So the vote passed, now it's time for volunteers to use their >> >>> > fingers >> >>> :-). >> >>> > I have started a page [1] for ETA of migration (note the Volunteer >> >>> > column :-) ) and for discussion on some stuff (plugins shared) >> >>> > >> >>> > >> >>> > Thanks >> >>> > -- >> >>> > Olivier Lamy >> >>> > Talend: http://coders.talend.com >> >>> > http://twitter.com/olamy | http://linkedin.com/in/olamy [1] >> >>> > https://cwiki.apache.org/confluence/display/MAVEN/Git+Migration >> >>> >> >>> -- >> >>> Baptiste <Batmat> MATHUS - http://batmat.net Sauvez un arbre, Mangez >> >>> un castor ! >> >>> nbsp;! >> >>> <https://cwiki.apache.org/confluence/display/MAVEN/Git+Migration> >> >>> >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For >> > additional commands, e-mail: dev-h...@maven.apache.org >> > >> >> >> >> -- >> Olivier Lamy >> Talend: http://coders.talend.com >> http://twitter.com/olamy | http://linkedin.com/in/olamy >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional >> commands, e-mail: dev-h...@maven.apache.org > > > ________________________________ > > > ************************************************************************************** > This message is confidential and intended only for the addressee. If you have > received this message in error, please immediately notify the > postmas...@nds.com and delete it from your system as well as any copies. The > content of e-mails as well as traffic data may be monitored by NDS for > employment and security purposes. To protect the environment please do not > print this e-mail unless necessary. > > NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 > 4EX, United Kingdom. A company registered in England and Wales. Registered > no. 3080780. VAT no. GB 603 8808 40-00 > ************************************************************************************** > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
