[arch-dev-public] Fwd: Killing CVS [was: Status Report 2007-10-15]
Figured I'd forward this on to the list- it could strike up a discussion. I've looked at git-submodules, but it is quite new, and not all that lightweight as each submodule has its own .git directory. -Dan ---------- Forwarded message ---------- From: Loui <louipc.ist@gmail.com> Date: Oct 22, 2007 9:06 PM Subject: Re: [arch-dev-public] Killing CVS [was: Status Report 2007-10-15] To: dpmcgee@gmail.com Do you think git submodules could be useful or relevant considering the 'Killing CVS' topic? In terms of checking out individual packages. http://www.kernel.org/pub/software/scm/git/docs/user-manual.html#submodules "Large projects are often composed of smaller, self-contained modules. For example, an embedded Linux distribution's source tree would include every piece of software in the distribution with some local modifications; a movie player might need to build against a specific, known-working version of a decompression library; several independent programs might all share the same build scripts."
On Mon, Oct 22, 2007 at 09:35:10PM -0500, Dan McGee wrote:
Figured I'd forward this on to the list- it could strike up a discussion.
I've looked at git-submodules, but it is quite new, and not all that lightweight as each submodule has its own .git directory.
-Dan
---------- Forwarded message ---------- From: Loui <louipc.ist@gmail.com> Date: Oct 22, 2007 9:06 PM Subject: Re: [arch-dev-public] Killing CVS [was: Status Report 2007-10-15] To: dpmcgee@gmail.com
Do you think git submodules could be useful or relevant considering the 'Killing CVS' topic? In terms of checking out individual packages.
I'd be very afraid of the overhead of managing all those git repositories (one per package) as Dan said. Not only that but a release is a commit, push, update submodule definition, commit. Jason
participants (2)
-
Dan McGee
-
Jason Chu