Sven Verdoolaege [off-list ref] writes:
I'm obviously not going to stop anyone from putting URLs in .gitmodules
and I can see that it would be useful in practice, but I still think
that it doesn't matter where the submodule was located at any
given point in history (from the point of view of the superproject).
It only matters where the submodule is located now.
You may be bisecting a problem and you may need to clone a submodule
for a point in history when the submodule was placed somewhere else.
(You may not have had a need to checkout the submodule before,
or it may simply not be used in the current version of the supermodule.)
So, I think it would still be useful to have an optional additional
out-of-tree mechanism of getting usable URLs if the URLs in .gitmodules
or your local config don't work.
I thought that was already solved in my original two-level
strawman and can naturally be extended to the three-level
strawman. What am I missing?
gmane=http://article.gmane.org/gmane.comp.version-control.git/
$gmane/47502
$gmane/47548
$gmane/47621
On Fri, May 25, 2007 at 09:16:30AM -0700, Junio C Hamano wrote:
Sven Verdoolaege [off-list ref] writes:
quoted
So, I think it would still be useful to have an optional additional
out-of-tree mechanism of getting usable URLs if the URLs in .gitmodules
or your local config don't work.
I thought that was already solved in my original two-level
strawman and can naturally be extended to the three-level
strawman. What am I missing?
Maybe I'm missing something but you only seem to talk about .gitmodules
and local config there, while this would be a way of automatically getting
URLs that are either not available in .gitmodules or the local config
or are outdated or should be overridden.
skimo
Hi,
On Fri, 25 May 2007, Sven Verdoolaege wrote:
On Fri, May 25, 2007 at 09:16:30AM -0700, Junio C Hamano wrote:
quoted
Sven Verdoolaege [off-list ref] writes:
quoted
So, I think it would still be useful to have an optional additional
out-of-tree mechanism of getting usable URLs if the URLs in .gitmodules
or your local config don't work.
I thought that was already solved in my original two-level
strawman and can naturally be extended to the three-level
strawman. What am I missing?
Maybe I'm missing something but you only seem to talk about .gitmodules
and local config there, while this would be a way of automatically getting
URLs that are either not available in .gitmodules or the local config
or are outdated or should be overridden.
I do not see what you're getting at.
Either you want to fetch the URLs from an upstream, in which case they
should be fetched. Why not in ".gitmodules"? If the URLs don't work, you
should blame the maintainer, not fsck up the tool.
Or you want some sort of "fallback" set of URLs. I cannot think of any
reasonable use case here.
Or you want to receive overrides, such as when a submodule has moved, so
that it still works when you check out older versions (and do not have the
objects locally already). But to make such overrides automatic wreaks
havoc IMHO.
Also, this is rare enough that I'd rather not fsck up an elegant solution,
where you have to treat such special cases manually, for something which
affects "normal" users, which just track the project.
Maybe I'm wrong. But then, Josef is right, we can talk about that later.
It's not like you need a feature like that from day one.
Ciao,
Dscho