git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Matthieu Moy <Matthieu.Moy@imag.fr>
Cc: "Jon Smirl" <jonsmirl@gmail.com>, "Jeff King" <peff@peff.net>,
	"Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
	"Git Mailing List" <git@vger.kernel.org>
Subject: Re: Cloning from kernel.org, then switching to another repo
Date: Tue, 13 Nov 2007 11:13:15 -0800	[thread overview]
Message-ID: <7vy7d2rmb8.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <vpq3avah3r0.fsf@bauges.imag.fr> (Matthieu Moy's message of "Tue, 13 Nov 2007 10:52:03 +0100")

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

> "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.

  reply	other threads:[~2007-11-13 19:16 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-12 13:57 Cloning from kernel.org, then switching to another repo Jon Smirl
2007-11-12 14:13 ` Johannes Schindelin
2007-11-12 15:36   ` Jon Smirl
2007-11-12 16:16     ` Johannes Schindelin
2007-11-12 16:22       ` Jon Smirl
2007-11-12 16:36         ` Johannes Schindelin
2007-11-12 17:21           ` Jon Smirl
2007-11-12 17:28             ` Jon Smirl
2007-11-13  4:14               ` Jeff King
2007-11-13  4:20             ` Jeff King
2007-11-13  4:30               ` Jon Smirl
2007-11-13  4:48                 ` Jeff King
2007-11-13  9:52                 ` Matthieu Moy
2007-11-13 19:13                   ` Junio C Hamano [this message]
2007-11-13 19:27                     ` Jon Smirl
2007-11-13 19:33                       ` Jakub Narebski
2007-11-12 20:31   ` Linus Torvalds
2007-11-12 20:42     ` Johannes Schindelin
2007-11-12 20:54       ` Jon Smirl
2007-11-13  4:23         ` Jeff King
2007-11-13  4:33           ` Jon Smirl
2007-11-12 20:51     ` Jon Smirl

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7vy7d2rmb8.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=Matthieu.Moy@imag.fr \
    --cc=git@vger.kernel.org \
    --cc=jonsmirl@gmail.com \
    --cc=peff@peff.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).