Re: dumb transports not being welcomed..

From: Junio C Hamano <junkio@cox.net>
Date: Sep 14, 2005, 19:00 UTC
Message-ID: <7vk6hjiiew.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <1126707016.14036.14.camel@cashmere.sps.mot.com>

Jon Loeliger <jdl@freescale.com> writes:

Show 5 quoted lines

> Well, that is sort of just it, too.  Why not make the
> default, obvious, common repo prep mechanism do all
> the necessary steps for proper presentation?  Having
> to remember to do 6 steps just begs for an additional
> layer of scripting.

Fair enough. My excuse is that Linus did not want the update-server-info hook enabled by default. He does not believe in dumb transports anyway, but aside from that, it still is a valid attitude because it is not necessary when you do not intend to publish your repository over dumb transport at all but still want to push into it. And another excuse is I do not in general think enabling hooks by default is a good idea.

Even if you built your repository with older git tools, you should be always able to say 'GIT_DIR=that-repository git-init-db' without damaging its existing contents to install the disabled hooks in its hooks/ directory.

> I confess, I've been using rsync as it is what appears
> to be able to reliably get a repository that works.

And I thought rsync was a reliable way too, until I saw a message from Tony Luck this morning X-<.