From: Junio C Hamano <junkio@cox.net>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Josef Weidendorfer <Josef.Weidendorfer@gmx.de>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] Added hook in git-receive-pack
Date: Sun, 31 Jul 2005 13:33:58 -0700 [thread overview]
Message-ID: <7vr7ded8ax.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0507311305170.29650@g5.osdl.org> (Linus Torvalds's message of "Sun, 31 Jul 2005 13:11:58 -0700 (PDT)")
Linus Torvalds <torvalds@osdl.org> writes:
> This looks sane. However, I also get the strong feeling that
> git-update-server-info should be run as part of a hook and not be built
> into receive-pack..
> Personally, I simply don't want to update any dumb server info stuff for
> my own local repositories - it's not like I'm actually serving those out
> anyway.
But you are. I can run this just fine:
$ git clone http://www.kernel.org/pub/scm/linux/kernel/git/torvalds/git.git/ linus
I agree in principle that you should be able to disable the call
to update_server_info() from there, but on the other hand once
we start doing it, we need to explain people which repo is http
capable and which repo is not and why.
I was actually thinking about a call to git-update-server-info
at the end of git-repack-script. Again, great minds think the
opposite way sometimes ;-).
next prev parent reply other threads:[~2005-07-31 20:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-31 19:17 [PATCH] Added hook in git-receive-pack Josef Weidendorfer
2005-07-31 20:11 ` Linus Torvalds
2005-07-31 20:33 ` Junio C Hamano [this message]
2005-07-31 22:50 ` Linus Torvalds
2005-07-31 23:24 ` Junio C Hamano
2005-07-31 23:31 ` Johannes Schindelin
2005-07-31 23:33 ` Linus Torvalds
2005-08-01 0:11 ` Junio C Hamano
2005-08-01 0:25 ` Linus Torvalds
2005-07-31 20:15 ` Junio C Hamano
2005-07-31 23:17 ` Josef Weidendorfer
2005-08-01 8:14 ` Junio C Hamano
2005-08-13 18:31 ` Josef Weidendorfer
2005-08-13 19:27 ` Junio C Hamano
2005-08-13 20:39 ` Josef Weidendorfer
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=7vr7ded8ax.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=Josef.Weidendorfer@gmx.de \
--cc=git@vger.kernel.org \
--cc=torvalds@osdl.org \
/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).