On 7/31/08, Björn Steinbrink <B.Steinbrink@gmx.de> wrote:
quoted text
>  Maybe even better:
>
>  mkdir local-mirror
>  cd local-mirror
>  git --bare init
>  git remote add -f --mirror origin <central-repo-over-network>
>
>  A cronjob (or whatever) could keep the local mirror up-to-date and the
>  other repos can fetch from there. Pushing would need to go to a
>  different remote then though.. Humm... Maybe not worth the trouble for a
>  bit of additional object sharing.

What would be *really* great is if we could find a way for multiple
local clones to share the same objects, refs, and configuration - ie.
without pushing and pulling between them at all.  Then they could
*all* point at the remote upstream repo through "origin", and
pushing/pulling with that repo would update the objects and refs for
all the local repos.

I'm not sure of the best way to do this, though.  In particular, it
seems like having multiple work trees checked out on the same ref
could be problematic.

Is that just what git-new-workdir is for?  (It seems to be
undocumented so it's hard to tell.)  And what about this
.gitlink/.gitfile stuff I've heard about?  Could I use that to have
multiple work trees share the same .git folder?

Thanks,

Avery
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html