On 23.10.2011 11:34, Emilian Huminiuc wrote: > That could have been avoided by having the aircraft dir itself in the > repository tree: > > aircraft-repository/AIRCraft-name/aircraft-subtree > > in place of the current solution of: > > aircraft-repository/aircraft subtree > > as can be seen here: https://gitorious.org/iar80/iar80-repo/trees/master
Unfortunately, that would make it impossible to ever use "git submodules". With the current solution, we could create a "super repo" referencing all or a collection of aircraft. We could also share the base package aircraft into fgdata etc. When a git submodule is referenced, the referencing repository creates a new directory containing the submodule, i.e. fgdata/Aircraft/UFO => git://gitorious.org/flightgear-aircraft/ufo.git When there was a "UFO" directory inside the ufo.git, we would get an "Aircraft/UFO/UFO/..." structure - which wouldn't work. So, it's important that the aircraft directory name isn't part of the submodules' directory structure. But indeed, that's also not so nice - another issue not really working well. cheers, Thorsten ------------------------------------------------------------------------------ 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@Cisco 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
