river-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bryan Thompson <br...@blazegraph.com>
Subject Re: Fwd: [jira] [Updated] (INFRA-12432) Apache River migration from SVN to Git - Git commit access
Date Fri, 09 Sep 2016 11:14:32 GMT
I have become significantly pro-git over the last few years.  I feel that
it is much more nimble, and I think the goal here is to help make river
more modular and gain the ability for an improved pace of development.

Can you expand on your objection about scripts and complexity incurred?

Bryan

On Fri, Sep 9, 2016 at 1:40 AM, Simon IJskes - QCG <simon@qcg.nl> wrote:

> If any, please dont.
>
> The amount of scripting or addons that is needed to have multiple repos
> integrated does not outweigh the perceived benefits of git.
>
> The amount of work in forking, pushing, merging etc. is a lot compared to
> subversion commits.
>
> You can have your own git, sync it with subversion, and back patch the
> changes into subversion.
>
> So you can still have your own git, and have subversion for the project.
>
> OK, subversion is not as nimble as git. But so fast we are not really
> going are we?
>
> G. Simon
>
> On 08-09-16 06:01, Peter wrote:
>
>> Anyone have thougts on this?
>>
>> Sent from my Samsung device.
>>
>>   Include original message
>> ---- Original message ----
>> From: Chris Lambertus (JIRA) <jira@apache.org>
>> Sent: 08/09/2016 10:48:21 am
>> To: jini@zeus.net.au
>> Subject: [jira] [Updated] (INFRA-12432) Apache River migration from SVN
>> to Git - Git commit access
>>
>>
>>      [ https://issues.apache.org/jira/browse/INFRA-12432?page=com.
>> atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>>
>> Chris Lambertus updated INFRA-12432:
>> ------------------------------------
>>     Status: Waiting for user  (was: Waiting for Infra)
>>
>> This will be complicated and time consuming as the svn repo doesn't fit
>> the usual trunk/branches/tags format. You may want to do some consolidation
>> or break this down into multiple git repos, for example, river-site.git,
>> river-rt-tools.git, etc. prior to us doing an SVN->Git migration. If you'd
>> rather have it all in one repo, let us know and we'll see what we can do.
>>
>>
>>  Apache River migration from SVN to Git - Git commit access
>>>  ----------------------------------------------------------
>>>
>>>                  Key: INFRA-12432
>>>                  URL: https://issues.apache.org/jira/browse/INFRA-12432
>>>              Project: Infrastructure
>>>           Issue Type: New Git Repo
>>>           Components: Git
>>>             Reporter: Peter Firmstone
>>>
>>>
>>
>>
>>
>>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message