We can't touch Apache's SVN so it definitely stays! :)
This was also something that crossed my mind -- we effectively have
multiple separate projects in one git repo. While it's something SVN can
take, it's a more problematic issue with git. I don't know if one Apache
project can have multiple
> I personally don't care. Git has been a non-issue in PyLucene.
> It can move with Lucene or stay in SVN, either way is fine by me.
I don't see a problem with it staying in SVN, we'd just clean up dev, much
like it has been done before when Solr and Lucene were merged (in fact,
this is what you
One project can have multiple git repos. Apparently there's one or
more with 100+ repos, so all is good there if pylucene wants to shift
to git also.
Upayavira
On Wed, Dec 16, 2015, at 09:48 PM, Dawid Weiss wrote:
>
>> I personally don't care. Git has been a non-issue in PyLucene.
>>
It can
On Wed, 16 Dec 2015, Dawid Weiss (JIRA) wrote:
[
https://issues.apache.org/jira/browse/LUCENE-6933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dawid Weiss updated LUCENE-6933:
Description:
Goals:
* selectively drop projects
On Wed, 16 Dec 2015, Dawid Weiss wrote:
We can't touch Apache's SVN so it definitely stays! :)
This was also something that crossed my mind -- we effectively have
multiple separate projects in one git repo. While it's something SVN can
take, it's a more problematic issue with git. I don't
