From: Theodore Tso <tytso@mit.edu>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jon Smirl <jonsmirl@gmail.com>, Jeff King <peff@peff.net>,
jnareb@gmail.com, Nicolas Pitre <nico@cam.org>,
"Shawn O. Pearce" <spearce@spearce.org>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: git-daemon on NSLU2
Date: Mon, 27 Aug 2007 07:03:18 -0400 [thread overview]
Message-ID: <20070827110318.GB4680@thunk.org> (raw)
In-Reply-To: <alpine.LFD.0.999.0708261118260.25853@woody.linux-foundation.org>
On Sun, Aug 26, 2007 at 11:26:07AM -0700, Linus Torvalds wrote:
> > How about changing initial clone to refuse to use the git protocol?
>
> Absolutely not. It's quite often the best one to use (the ssh protocol
> has the exact same issues, and is the only secure protocol).
>
> But on a SNLU2, maybe *you* want to make your server side refuse it? I
> would be easy enough: if the client doesn't report any existing SHA1's,
> you just say "I'm not going to work with you".
What if the server sends a message which current clients interprets as
an error, and which newer clients could interpret as, "do a clone from
<this> URL, and then come back and talk to me". Basically an
automated redirect to get the "Linus base pack" somewhere else, and
then to go back to the original server. It certainly doesn't make
sense to change anything about the low-level protocol, but maybe a
higher level redirect would make sense, just as a user convenience thing.
- Ted
next prev parent reply other threads:[~2007-08-27 11:03 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-24 5:54 git-daemon on NSLU2 Jon Smirl
2007-08-24 6:21 ` Shawn O. Pearce
2007-08-24 19:38 ` Jon Smirl
2007-08-24 20:23 ` Nicolas Pitre
2007-08-24 21:17 ` Jon Smirl
2007-08-24 21:54 ` Nicolas Pitre
2007-08-24 22:06 ` Jon Smirl
2007-08-24 22:39 ` Jakub Narebski
2007-08-24 22:59 ` Junio C Hamano
2007-08-24 23:21 ` Jakub Narebski
2007-08-24 23:46 ` Jon Smirl
2007-08-25 0:04 ` Junio C Hamano
2007-08-25 7:12 ` David Kastrup
2007-08-25 17:02 ` Salikh Zakirov
2007-08-25 0:10 ` Nicolas Pitre
2007-08-24 23:28 ` Linus Torvalds
2007-08-25 15:44 ` Jon Smirl
2007-08-26 9:33 ` Jeff King
2007-08-26 16:34 ` Jon Smirl
2007-08-26 17:15 ` Linus Torvalds
2007-08-26 18:06 ` Jon Smirl
2007-08-26 18:26 ` Linus Torvalds
2007-08-26 19:00 ` Jon Smirl
2007-08-26 20:19 ` Linus Torvalds
2007-08-26 21:22 ` Junio C Hamano
2007-08-27 11:03 ` Theodore Tso [this message]
2007-08-27 16:26 ` Linus Torvalds
2007-08-26 22:24 ` Daniel Hulme
2007-08-27 0:14 ` Jakub Narebski
2007-08-24 20:27 ` 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070827110318.GB4680@thunk.org \
--to=tytso@mit.edu \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=jonsmirl@gmail.com \
--cc=nico@cam.org \
--cc=peff@peff.net \
--cc=spearce@spearce.org \
--cc=torvalds@linux-foundation.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).