Ah, I see - that makes sense. It is tricky to nest git repositories within one another. There are some drawbacks to your approach - namely that the '--depth' option will create a shallow clone. According to the git-clone manual:
'A shallow repository has a number of limitations (you cannot clone or fetch from it, nor push from nor into it), but is adequate if you are only interested in the recent history of a large project with a long history, and would want to send in fixes as patches.'
So if you don't plan to clone from your local repo or to submit patches, you should be fine. Otherwise, you will need to try another approach.
To get around this on one of my dev setups, I solve this problem slightly differently. I have Mediawiki core checked out to one directory, and all of my extensions checked out into a completely different directory - eg ~/Dev/wikimedia_git/mediawiki and ~/Dev/wikimedia_git/extensions/ respectively. I then symlink individual extensions to the Mediawiki install. This keeps the repositories independent, however there are some nuances with this approach that can also get you into trouble. Namely if you ever check out a branch of the mediawiki repository that as things already in the 'extensions' directory, you may get all your symlinks overwritten.
How do other folks deal with this?
On Mon, Apr 7, 2014 at 9:23 PM, 積丹尼 Dan Jacobson jidanni@jidanni.orgwrote:
The problem is if the user has already cloned wikimedia in the main directory, and now clones MobileFrontend to the extensions directory, any git pulls even in the extensions directory will only update the main directory.