Re: Cloning from kernel.org, then switching to another repo

From: Junio C Hamano <gitster@pobox.com>
Date: Nov 13, 2007, 19:13 UTC
Message-ID: <7vy7d2rmb8.fsf@gitster.siamese.dyndns.org>
In-Reply-To: <vpq3avah3r0.fsf@bauges.imag.fr>

Matthieu Moy <Matthieu.Moy@imag.fr> writes:

Show 13 quoted lines

> "Jon Smirl" <jonsmirl@gmail.com> 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.