Re: [git-users] Large SVN to GIT migration

2016-11-03 Thread Kevin Norton
Thanks Mark, All advice so far seems to trend towards taking opportunity to clean up repository. I'm doing a walk through Clone of latest Dev Branch into GIT. I want to see how to manage the Clone and then keep synchronized. And then evenutally push or clone into a central repository that

Re: [git-users] Large SVN to GIT migration

2016-11-03 Thread Mark Waite
On Thursday, November 3, 2016 at 10:31:08 AM UTC-6, Kevin Norton wrote: > > Thanks Magnus, > > i will explore subgit, but i think i'm leaning towards simplifying my repo > and trimming un-needed branches and history. > When we did a major transition from a previous source control system to

Re: [git-users] Best Practices around version control / configuration management of Python / Spark Machine Learning Models on Git

2016-11-03 Thread Nelson Efrain A. Cruz
Well I think that in the end it's just code, maybe the difference it's that this code changes very often. Just make a commit every time you achieve something (or some task is completed). If you are worried about having different versions of a same model, you can use branches to keep them

[git-users] Best Practices around version control / configuration management of Python / Spark Machine Learning Models on Git

2016-11-03 Thread Debabrata Ghosh
Hi, Greetings ! I need certain best practices / guidance around how to effectively version control advance analytical models written in Python / Spark on Git. The advanced analytical models are a bit different to the normal Java code. As the training of the

[git-users] Re: Large SVN to GIT migration

2016-11-03 Thread Kevin Norton
Thanks Nando, I have attempted clone of entire repo. Basically i believe it will complete most likely afer a few days of restarts after failures. But most likely i need to take this opportunity to trim my repo and only clone what is necessary. Old versions of code are most likely not

Re: [git-users] Large SVN to GIT migration

2016-11-03 Thread Kevin Norton
Thanks Magnus, i will explore subgit, but i think i'm leaning towards simplifying my repo and trimming un-needed branches and history. Kevin On Thursday, November 3, 2016 at 1:18:53 AM UTC-7, Magnus Therning wrote: > > > Kevin Norton writes: > > > i'm in the process of

Re: [git-users] Yet more git madness

2016-11-03 Thread Paul Smith
On Tue, 2016-11-01 at 15:36 -0700, AD S wrote: > Sorry, I meant pull request. Everyone else's code (2,800+ files and > 250+ commits) are suddenly in the pull request I was working on (which > had 8 files and 4 commits).  As mentioned this seems more a rant about GitHub and its development model

Re: [git-users] Large SVN to GIT migration

2016-11-03 Thread Magnus Therning
Kevin Norton writes: > i'm in the process of coming up with a strategy to convert a very large > project from SVN to GIT. > > i'm experimented with git svn clone but have some questions. > > how large is to large. > > current SVN repo > 80K+ revisions. > suffers from

Re: [git-users] Large SVN to GIT migration

2016-11-03 Thread Magnus Therning
Kevin Norton writes: > i'm in the process of coming up with a strategy to convert a very large > project from SVN to GIT. > > i'm experimented with git svn clone but have some questions. > > how large is to large. > > current SVN repo > 80K+ revisions. > suffers from

Re: [git-users] What is git doing with "git submodule update" that I get coo-coo error: "outside repository"

2016-11-03 Thread Magnus Therning
Xtian Simon writes: > I'm getting this rather coo-coo error when using the Vim package manager > [Vundle][1]'s :PluginUpdate command. If you're not familiar with Vundle, it > lets you update your Vim plugin git packages. > > I've narrowed the problem down to the `submodule

[git-users] Re: Large SVN to GIT migration

2016-11-03 Thread Ferdinando Santacroce
Hi Kevin. Il giorno mercoledì 2 novembre 2016 19:48:58 UTC+1, Kevin Norton ha scritto: > > i'm in the process of coming up with a strategy to convert a very large > project from SVN to GIT. > > i'm experimented with git svn clone but have some questions. > > how large is to large. > > current