Hi, On Sat, 10 May 2008, Jeremy Maitin-Shepard wrote: > Jeff King <peff@xxxxxxxx> writes: > > > On Fri, May 09, 2008 at 09:51:15PM -0400, Jeremy Maitin-Shepard wrote: > >> When you create a new working directory, you would also create in the > >> original repository a symlink named > >> e.g. orig_repo/.git/peers/<some-arbitrary-name-that-doesn't-matter> that > >> points to the .git directory of the newly created working directory. > > > That assumes you _can_ write to the original repository. That may or may > > not be the case, depending on your setup. FWIW this argument can be found in the mailing list. It does not have to be told over and over again, right? > Well, I suppose in that case it could print a warning or maybe fail > without some "force" option. If you can't write to the repository, then > I think it is safe to say that it will never know or care about you, so > you will fundamentally have a fragile setup. I'd say that except in > very special circumstances, you are better off just not sharing it at > all. Counterexample kernel.org. Counterexample repo.or.cz. Hth, Dscho -- 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
