On Mon, Sep 28, 2009 at 7:31 AM, Adam Brewster <adambrewster@xxxxxxxxx> wrote: >> As git is used more and more in corporate-type environments, at some >> point it becomes convenient to have *branches* (or more accurately, >> refs) that are not readable. The simplest way to do this (from git's >> point of view) is to allow a "pre-upload" hook, rather like the >> "pre-receive" hook or "update" hook. >> > > What's the benefit of this over using multiple repositories? Over a long pm chat over irc with Ilari, I have come to the same conclusion. I was hoping there would be some administrative convenience or workflow convenience to doing this, but whether there is or not is debatable, and even if there is, there are enough failure modes to make this have a lot of caveats. -- Sitaram -- 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