[
https://issues.apache.org/jira/browse/LUCENE-6933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15058546#comment-15058546
]
Mark Miller commented on LUCENE-6933:
-------------------------------------
For some reference, here is a wiki page managing Mavens migration to git:
https://cwiki.apache.org/confluence/display/MAVEN/Git+Migration
Here is one of the infra JIRA's:
https://issues.apache.org/jira/browse/INFRA-5266 Migrate Maven subprojects to
git (surefire,scm,wagon)
Not all very relatable to us in a lot of ways, but a root to get into INFRA
tickets for a past migration.
> Create a (cleaned up) SVN history in git
> ----------------------------------------
>
> Key: LUCENE-6933
> URL: https://issues.apache.org/jira/browse/LUCENE-6933
> Project: Lucene - Core
> Issue Type: Task
> Reporter: Dawid Weiss
> Assignee: Dawid Weiss
>
> Goals:
> - selectively drop unnecessary stuff from history (cms/, javadocs/, JARs and
> perhaps other binaries),
> - *preserve* history of all core sources. So svn log IndexWriter has to go
> back all the way back to when Doug was young and pretty. Ooops, he's still
> pretty of course.
> - provide a way to link git history with svn revisions. I would, ideally,
> include a "imported from svn:rev XXX" in the commit log message.
> - annotate release tags and branches. I don't care much about interim
> branches -- they are not important to me (please speak up if you think
> otherwise).
> Non goals
> - no need to preserve "exact" history from SVN (the project may skip JARs,
> etc.). Ability to build ancient versions is not an issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
