Hi AJ, hi Martin
I see the advantages of GIT, no need to be convinced of that.
And I've had a look at the GIT projects on mapserver, very nice, and
it's already split into source and data!!!
But let's say that the project switched completely to GIT, would there
be a way to support streaming scenery ('terrasync') to the user without
him/her needing to clone the entire fgdata repository ?
Something like git-svnserve?!?
Tom
AJ MacLeod wrote:
On Wednesday 02 September 2009 22:44:56 Tom P wrote:
Yes, I agree, a distributed system is overkill for the data portion.
I would disagree...
1) data is handled well by a lightweight client-server model (either CVS
or SVN) that:
- allows users and developers to synchronize their local data set,
simply and quickly
With the data tree, we frequently have several people working on the same area
(aircraft models, in particular) - not only that, but many of the people
working on aircraft models have historically not had any kind of commit
access to the main repository. The line between user and developer is very
blurred in the data tree... which is why something like git seems to me to be
perfectly suited to the job.
As I see it, switching to a distributed model such as Git would allow people
like me who have no commit access to the main repo to maintain their own work
under a nice version control system, greatly improve the ease of
collaboration with other people working on the same models, and reduce the
need for each individual modeller to have full commit rights (by making
merging so much easier for those who do have them).
I switched to using the mapserver git repo for the data tree quite some time
ago, and the improvements for a modeller like me were massive. No more lost
work (I often had CVS completely botch my local changes), and all my own
local changes nicely version controlled with an easy to follow history.
- doesn't need advanced support for branching and merging
I would strongly disagree with that, from several years' experience
collaborating on models for FG...
In case it wasn't clear by now... I think we should be using git for both
source and data - as previously mentioned, many (if not most) FG developers
are already using it (though missing many benefits that would arise from the
main repo being git).
Cheers,
AJ
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
