I may have missed something, but I didn't see a proposal for dealing
with the comment:
"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,
Are there any remaining objections to git migration?
If so, lets discuss.
Regards,
Peter.
Sent from my Samsung device.
Include original message
Original message
From: Daniel Takamori (JIRA)
Sent: 29/09/2016 03:52:20 am
To: j...@zeus.net.au
Subject: [jira]
;si...@qcg.nl>
Sent: 14/09/2016 06:17:27 pm
To: dev@river.apache.org
Subject: Re: Fwd: [jira] [Updated] (INFRA-12432) Apache River migration from
SVN to Git - Git commit access
On 13-09-16 13:57, Peter wrote:
>
> I don't have strong feelings about it, I have heard that git history isn
On 13-09-16 13:57, Peter wrote:
I don't have strong feelings about it, I have heard that git history isn't as
good as svn, but merge is much better. I know we've had merge issues in the
past with svn, but I haven't experienced history issues with git yet.
dont overestimate the power of
:28 pm
To: dev@river.apache.org
Subject: Re: Fwd: [jira] [Updated] (INFRA-12432) Apache River migration from
SVN to Git - Git commit access
Could you make a proposal how to arrange the git repo(s)?
Please mitigate for:
http://programmers.stackexchange.com/questions/206668/using-multip
Could you make a proposal how to arrange the git repo(s)?
Please mitigate for:
http://programmers.stackexchange.com/questions/206668/using-multiple-git-repositories-instead-of-a-single-one-containing-many-apps-fro
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
o: dev@river.apache.org
Subject: Re: Fwd: [jira] [Updated] (INFRA-12432) Apache River migration from
SVN to Git - Git commit access
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 o
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