On Thu, 20 Oct 2011, Martin Spott wrote:
Jari Häkkinen wrote:
I support the split if only for the reason that aircraft maintainers
will get commit rights to their private spheres in fg-land (if I
understand things properly). With the previous monolithic fgdata only a
selected group of people had commit privileges.
Maybe now, that 'fgdata' is open again, one of the admins should simply
add Jari to the list of data maintainers ;-)
Still, that is a point in favour of having aircraft in separate
repositories. Already with our selected group there as been some scary git
moments, e.g. at one point a commit adding a new aircraft was undone in a
tangled mess of merges and remerges by other committers - but I do
sincerely hope that was only possible due to Tim having forgot to
forbid non-fastforward updates on fgdata at that point (which was
the case IIRC).
An other thing: we know a 4GB repository works well on at least some
platforms (e.g. I have had no problems) but what size is too large?
8GB? 16GB?
Nevermind, keeping everything in one repository we are likely to hit
that size sooner than if we scale in the number of repositories instead.
The latter carries its own problems as has been mentioned, however.
Amazingly, having both the new (experimental) and old fgdata master
branches in my git repository the size has not increased much:
anders@sleipner:~/FlightGear/fgdata$ du -sk .git
4022072 .git
The level of compression achieved by git is impressive, but no doubt
helped by the identical deltas on the respective branches.
Cheers,
Anders
--
---------------------------------------------------------------------------
Anders Gidenstam
WWW: http://www.gidenstam.org/FlightGear/
http://gitorious.org/anders-hangar------------------------------------------------------------------------------
The demand for IT networking professionals continues to grow, and the
demand for specialized networking skills is growing even more rapidly.
Take a complimentary Learning@Ciosco Self-Assessment and learn
about Cisco certifications, training, and career opportunities.
http://p.sf.net/sfu/cisco-dev2dev
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
