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 Dev
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
git
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 coming up with a strat
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 poor SCM practices
> current
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 poor SCM practices
> current
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 poor SCM practices
current structure in SVN is using cascading hier