On Thu, May 17, 2007 at 01:02:25PM CEST, Alex Riesen wrote: > why can't I just have _repo_ configuration: > > [subproject "kernel/"] > URL = http://www.kernel.org/pub/linux-2.6.git > ? > It can be first-time cloned from the upstream, but it stays after > people change it to suit their systems. They can depend on it not to > be broken by upstream. Because kernel/ can get removed, moved around, or point at entirely *different* projects over time and branches - kernel/ can switch from linux-2.4 to linux-2.6, libc/ can switch between glibc and uClibc, ... > Can I suggest a part of repo configuration to be clonable? So that > there is a something in .git/config.dist, which is _cloned_ with > git-clone. The obviuos thing to put there would be subproject > configuration, and maybe there will be something else in the future > (I'd think of description, which is a separate file now, and as for > now, the only way to get this description is to use gitweb or ssh). > git-ls-remote could be made to show this "remote-accessible" > configuration, in case someone have to update/compare local copy of > this config. This is troublesome because then you will also need a way to update the configuration in the future, otherwise you will run into some embarassing situations, and since we don't even support any motds while fetching, when something *needs* to be changed you don't even have a good way to tell your users. (Actually, I've been thinking about adding motd support to the fetchers. :-) -- Petr "Pasky" Baudis Stuff: http://pasky.or.cz/ Ever try. Ever fail. No matter. // Try again. Fail again. Fail better. -- Samuel Beckett - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
