This does seem strange. That behaviour was introduced in this commit : commit c2f939170c65173076bbd752bb3c764536b3b09b Author: Mark Levedahl Date: Wed Jul 9 21:05:41 2008 -0400 git-submodule - register submodule URL if adding in place When adding a new submodule in place, meaning the user created the submodule as a git repo in the superproject's tree first, we don't go through "git submodule init" to register the module. Thus, the submodule's origin repository URL is not stored in .
Git/config, and no subsequent submodule operation will ever do so. In this case, assume the URL the user supplies to "submodule add" is the one that should be registered, and do so. Signed-off-by: Mark Levedahl Signed-off-by: Junio C Hamano Com Update: you've pointed out in the comments below that my original interpretation of this commit message didn't make any sense, so I've removed that text now to avoid confusion for others As mentioned in the comments below cdwilson posted to the git mailing list to ask about this inconsistency, and as a result Jens Lehman is working on a fix - that thread can be found here: http://git.661346.n2.nabble.com/Why-does-adding-an-existing-repo-as-a-submodule-modify-git-config-td6392263.html.
This does seem strange. That behaviour was introduced in this commit: commit c2f939170c65173076bbd752bb3c764536b3b09b Author: Mark Levedahl Date: Wed Jul 9 21:05:41 2008 -0400 git-submodule - register submodule URL if adding in place When adding a new submodule in place, meaning the user created the submodule as a git repo in the superproject's tree first, we don't go through "git submodule init" to register the module. Thus, the submodule's origin repository URL is not stored in .
Git/config, and no subsequent submodule operation will ever do so. In this case, assume the URL the user supplies to "submodule add" is the one that should be registered, and do so. Signed-off-by: Mark Levedahl Signed-off-by: Junio C Hamano Update: you've pointed out in the comments below that my original interpretation of this commit message didn't make any sense, so I've removed that text now to avoid confusion for others.As mentioned in the comments below, cdwilson posted to the git mailing list to ask about this inconsistency, and as a result Jens Lehman is working on a fix - that thread can be found here: http://git.661346.n2.nabble.com/Why-does-adding-an-existing-repo-as-a-submodule-modify-git-config-td6392263.html.
Mark, thanks for the pointer to that commit (at least it shows this behavior is intentional). However, I'm still confused when you said "it isn't cloned until the submodule is updated". In the first case above, git submodule add git@git.
Server:submodule. Git actually clones submodule. Git into the super-project.In the examples above, the only submodule command I ran was git submodule add, and in both cases I ended up with a cloned submodule.
Git in my super-project. The only difference is what . Git/config looks like afterwards, and case #1 also needs git submodule init to register.
– cdwilson May 22 at 16:37 This behavior would make sense to me if, in the first case, git submodule add didn't clone the repository until the submodule was registered (git submodule init) and updated (git submodule update). However, since case #1 above actually does clone submodule. Git, and requires git submodule init to register, I would expect case #2 to require git submodule init as well to perform the registration.
I'm sure there is just something here that I'm missing, but right now I don't understand why there is a discrepancy. – cdwilson May 22 at 16:51 @cdwilson: Good point, I was misremembering the behaviour of git submodule add in my rush to answer the question. I'll correct my answer.
You could ask about this on the git mailing list for a proper answer - I suspect this is a bug, but perhaps I'm missing something. – Mark Longair May 22 at 17:01 posted to git mailing list permalink.gmane.Org/gmane.comp. Version-control.
Git/174199 – cdwilson May 220 at 6:19.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.