You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@infra.apache.org by "Dawid Weiss (JIRA)" <ji...@apache.org> on 2016/01/13 11:35:40 UTC
[jira] [Comment Edited] (INFRA-11056) Migrate Lucene project from
SVN to Git.
[ https://issues.apache.org/jira/browse/INFRA-11056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15095977#comment-15095977 ]
Dawid Weiss edited comment on INFRA-11056 at 1/13/16 10:35 AM:
---------------------------------------------------------------
I can't resist to ask -- would it be possible to have the same repo (git://git.apache.org/lucene-solr.git) and just overwrite it with new data? I understand this may be surprising for people who have forked it, but at the same time all they'd have to do would be to rebase their feature branches. We can warn about it on the list.
I would do a mirror push so that the current content (tags, branches) would be removed from lucene-solr.git; we'd effectively replace a (corrupted) git mirror with something that actually makes historical sense.
was (Author: dweiss):
I can't ask -- would it be possible to have the same repo (git://git.apache.org/lucene-solr.git) and just overwrite it with new data? I understand this may be surprising for people who have forked it, but at the same time all they'd have to do would be to rebase their feature branches. We can warn about it on the list.
I would do a mirror push so that the current content (tags, branches) would be removed from lucene-solr.git; we'd effectively replace a (corrupted) git mirror with something that actually makes historical sense.
> Migrate Lucene project from SVN to Git.
> ---------------------------------------
>
> Key: INFRA-11056
> URL: https://issues.apache.org/jira/browse/INFRA-11056
> Project: Infrastructure
> Issue Type: Task
> Components: Git
> Reporter: Mark Miller
> Assignee: Daniel Gruno
>
> The Lucene project was recently notified that our strategy for mirroring to Git from SVN was not sustainable. As a result, the project has decided to move from SVN to Git.
> Some committers had an issue with how large our history was in Git for various reasons, and so we have produced a cleaned up repo for our use.
> Relevant issues:
> LUCENE-6937: Migrate Lucene project from SVN to Git.
> LUCENE-6933: Create a (cleaned up) SVN history in git.
> We would like to take our cleaned up Git repo in LUCENE-6933 and move to it from our Apache SVN location.
> One of our subprojects, PyLucene, is happy to stick with it's spot in SVN. I think we probably want to make the rest of our SVN location read-only.
> Other Lucene committers will likely comment in further detail as necessary.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)