git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Jakub Narebski <jnareb@gmail.com>
Cc: Sam Vilain <sam@vilain.net>, Martin Mares <mj@ucw.cz>,
	Petr Baudis <pasky@suse.cz>,
	skimo@liacs.nl, git@vger.kernel.org
Subject: Re: repo.or.cz wishes?
Date: Mon, 27 Aug 2007 16:38:48 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LFD.0.999.0708271635170.25853@woody.linux-foundation.org> (raw)
In-Reply-To: <200708280127.47808.jnareb@gmail.com>



On Tue, 28 Aug 2007, Jakub Narebski wrote:
> 
> Not exactly. You can browse using http:// and file:// protocols,
> rsync:// is simply rsync, while ssh:// (or git_ssh://) can be limited
> using git-shell.

Bullshit. You carefully left out "git://", since that doesn't fit your 
"argument".

The fact is, all git URL's make sense for *git*, not necessarily for 
anything else. They may have incidental meanings outside of git, but 
certainly nothing that is really *sensible*.

And that is how it was designed to be. The URL's are for *git*, not for 
other uses. If you want to do cross-SCM tools, you need to let them know 
it's a "git" thing wheher it's browsable or not, so the argument that ssh 
is something "different" is bogus crapola.

Just face it, ssh is in no way different from any of the other git URL 
specifiers. 

			Linus

  reply	other threads:[~2007-08-27 23:40 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
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 [this message]
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.0708271635170.25853@woody.linux-foundation.org \
    --to=torvalds@linux-foundation.org \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    --cc=mj@ucw.cz \
    --cc=pasky@suse.cz \
    --cc=sam@vilain.net \
    --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).