git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Petr Baudis <pasky@suse.cz>
Cc: skimo@liacs.nl, git@vger.kernel.org, Jakub Narebski <jnareb@gmail.com>
Subject: Re: repo.or.cz wishes?
Date: Mon, 27 Aug 2007 11:23:52 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LFD.0.999.0708271114470.25853@woody.linux-foundation.org> (raw)
In-Reply-To: <20070827004153.GN1219@pasky.or.cz>



On Mon, 27 Aug 2007, Petr Baudis wrote:

> On Mon, Aug 27, 2007 at 02:16:34AM CEST, Sven Verdoolaege wrote:
> > On Mon, Aug 27, 2007 at 01:59:44AM +0200, Petr Baudis wrote:
> > >   So now I wonder, what is the thing you miss most there? Any cool stuff
> > > repo.or.cz could (preferrably easily) do and doesn't?
> > 
> > Just a minor nit, but how about dropping the "git+" from the
> > Push URL?
> 
> I'm a major proponent of the "git+"

I'd say "only", not "major".

It makes no sense.

> - it's just the correct thing to specify. ssh:// by itself means secure 
> _shell_

No it isn't, and no it doesn't.

It makes no sense what-so-ever.

"ssh://" is the *protocol*. What is actually done over the protocol is 
specified by the program.

This is not at all git specific. Try running "ssh" vs "scp" some day, and 
you'll notice the exact same thing: they both use the ssh _protocol_, but 
no, your statement that "ssh://" by itself means "secure _shell_" is total 
and utter garbage.

It means nothing at all of the kind. 

"ssh://" means the ssh protocol. It is that unambiguous, and that simple. 
Saying "git+ssh://" is totally idiotic, always has been, and always will 
be.

It's as stupid as it would be to require people to say

	scp cp+ssh://host/filename .

and nobody sane would *ever* advocate something that stupid. It's not how 
it's done.

So why do you continue to advocate "git+ssh://", when nobody else does, 
and several people have asked you not to.

And yes, I realize that SVN does it. SVN for some unfathomable reason uses 
"svn+ssh://", but let's face it, the SVN developers have neither taste nor 
brains. They don't know any better.

			Linus

  reply	other threads:[~2007-08-27 18:25 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-26 23:59 repo.or.cz wishes? Petr Baudis
2007-08-27  0:16 ` Sven Verdoolaege
2007-08-27  0:41   ` Petr Baudis
2007-08-27 18:23     ` Linus Torvalds [this message]
2007-08-27 18:58       ` Junio C Hamano
2007-08-27 19:09       ` Matthieu Moy
2007-08-27 20:05       ` Martin Mares
2007-08-27 21:27         ` Jing Xue
2007-08-27 22:27         ` Linus Torvalds
2007-08-27 22:58           ` Sam Vilain
2007-08-27 23:17             ` Linus Torvalds
2007-08-27 23:27               ` Jakub Narebski
2007-08-27 23:38                 ` Linus Torvalds
2007-08-27 23:30               ` Sam Vilain
2007-08-27 23:34                 ` Linus Torvalds
2007-08-27 23:16           ` Jakub Narebski
2007-08-27 21:58     ` Jakub Narebski
     [not found]       ` <20070828084939.GF1976MdfPADPa@greensroom.kotnet.org>
     [not found]         ` <200708282356.10605.jnareb@gmail.com>
2007-08-29  7:32           ` Sven Verdoolaege
2007-08-29 23:12             ` Jakub Narebski
2007-08-27  2:40 ` Sam Vilain
2007-08-27  8:35 ` Johannes Schindelin
     [not found]   ` <20070828041059.GK18160@spearce.org>
     [not found]     ` <20070828111913.GA31120@thunk.org>
     [not found]       ` <Pine.LNX.4.64.0708281230310.28586@racer.site>
     [not found]         ` <20070829042005.GT18160@spearce.org>
2007-08-29  9:54           ` Petr Baudis
     [not found]       ` <20070829041523.GS18160@spearce.org>
     [not found]         ` <7vr6lnszay.fsf@gitster.siamese.dyndns.org>
2007-08-29  9:58           ` Petr Baudis
2007-08-29 11:13         ` Theodore Tso
2007-08-31 21:09           ` Shawn O. Pearce
2007-08-29 17:11         ` Linus Torvalds
2007-09-01  2:58           ` Shawn O. Pearce
2007-08-27 19:49 ` Uwe Kleine-König

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=alpine.LFD.0.999.0708271114470.25853@woody.linux-foundation.org \
    --to=torvalds@linux-foundation.org \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    --cc=pasky@suse.cz \
    --cc=skimo@liacs.nl \
    /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).