On 20:55 Sat 06 Aug , Robin H. Johnson wrote: > Everything you have mentioned here was previously covered in the > discussions about Git conversion models. Please consult the history of > this list, as well as the -scm list. Additionally, a large discussion > about the pros and cons of all 3 models (package per repo, category > per repo, single repo) was had at the GSoC mentor summit last year, > and a number of the core Git developers were involved in the > discussion.
While noting the above [1 and its thread], I'd also like to point out that git submodules are conceptually a good fit but the implementation is lacking. Two examples: - Creating new submodules requires administrative rights on the server. You can't just add one and push it up. This could conceivably be fixed by a hook that ran a specific privileged command to add a submodule, but I'm not really sure how or whether it's currently possible given the times available to run hooks. - What we'd really want with submodules is to have the primary object storage shared in the master repo rather than in the submodule. That way we'd benefit from compression across packages, and furthmore, package moves wouldn't duplicate history. If you're interested in fixing the above problems as well as the ones that exist regardless of repo format (linked on the main tracker bug [2]), then submodules could become a better option. -- Thanks, Donnie Donnie Berkholz Council Member / Sr. Developer Gentoo Linux Blog: http://dberkholz.com 1. http://archives.gentoo.org/gentoo-scm/msg_98932c55ec10fcc5445ab950e62b12dc.xml 2. https://bugs.gentoo.org/show_bug.cgi?id=333531
pgp7n15SHaMHz.pgp
Description: PGP signature
