Michael Meeks venit, vidit, dixit 24.02.2011 17:39: > Hi Brian, > > First - it seems that the issue here was entirely bogus, not least > because we had a bug with re-writing these makefiles as we checked them > in; so hopefully only 2 issues pending ;-) > > Anyhow - I tried your kind advice: > > On Tue, 2011-02-22 at 10:55 -0500, Brian Gernhardt wrote: >> FYI: `git clone foo bar` will use hard-links to copy the object >> files and is both very fast and space efficient. (See the >> description of `--local` in git-clone(1), which is used by >> default for local repositories since git 1.5.3.) It's also >> guaranteed to work while the correctness of `cp -lR` depends >> on implementation details of git. > > Sounds like just what I need. Unfortunately, it didn't clone some of > the pieces I needed; eg. other configured remotes, I ended up with just > 'origin' - which was unexpected (and less wonderful than cp -lR ;-). > > Is that a feature ? Yes, because by cloning someone else's config they could make you do what they want (alias...). I think in your case you can just copy over the .git/config and maybe set up "alternates" so that you don't have to refetch the remote objects which are not referenced by local refs. (Alternatively, clone --mirror, then copy over config and turn into non bare.) Maybe we do need "clone --copy" or something as a safe version of "cp -al"? Michael -- 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