On 11/13/07, Junio C Hamano <gitster@xxxxxxxxx> wrote: > Matthieu Moy <Matthieu.Moy@xxxxxxx> writes: > > > "Jon Smirl" <jonsmirl@xxxxxxxxx> writes: > > > >> Execute bit was not set. I just set it for all the scripts. +x is not > >> getting turned on with a default git init-db. I just made a new repo > >> to check, no +x on the scripts. > > > > That's by design: "git init" gives you _example_ hooks, but they won't > > run until you activate them explicitely with the appropriate chmod. > > > > That said, I'm not sure there's a really good reason not to run > > update-server-info by default on push. It doesn't cost much and saves > > a lot of troubles for beginners. Perhaps there are cases where the > > performance cost is non-negligible. > > One incarnation of u-s-i we had in the past was quite a lot more > expensive, but we discarded the complexity, so I'd agree it > won't cost much in the current shape now. > > The expensive one tried to record information to help dumb > transports better, such as "if you have this revision then you > do not have to fetch that pack but instead fetch this", as we > were discussing packs that have objects from duplicated, > staggered ranges. The idea did not quite pan out. Could we add an alternates entry on the server that would cause the client to first go fetch all objects the alternate has, then come back and fetch from the initial server with a normal fetch? It's like a URL redirect. You wouldn't fetch heads or tags from the alternate, just all of the objects. -- Jon Smirl jonsmirl@xxxxxxxxx - 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
