Re: How is git used as other than the project's version control?

[Mike Ralphson <mike.ralphson@gmail.com>]

2009/4/27 John Dlugosz <JDlugosz@tradestation.com>:
> I'm interested in finding out how people use git "on the side", when it
> is not the project's actual version control system.

We have historically used a very simple pessimistic locking strategy
with our legacy platform source. Individual files or groups of files
are checked out to developers' home directories and they override
what's in the live area when that dev compiles and tests for
themselves.

I basically inserted git under this mechanism, thus allowing the
optional use of merge and integrate (lockless development),
topic-branches, tags etc. Git also functions as our tripwire solution
to ensure changes to that master shared repo have all been made
traceably.

Git effectively is the VCS now, as what was there before was only
barely acceptable when it came to accessing old versions etc, but if
you don't want to interact with git, you don't have to even know it's
there. Until it saves your arse.

Mike