LKML Archive on
help / color / mirror / Atom feed
From: Linus Torvalds <>
To: Bill Lear <>
Cc: Junio C Hamano <>,,
Subject: Re: [ANNOUNCE] GIT 1.5.0
Date: Wed, 14 Feb 2007 08:45:44 -0800 (PST)	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Wed, 14 Feb 2007, Bill Lear wrote:
> This is enabled by passing the --enable=receive-pack to the
> git-daemon (usually in the [x]?inetd configuration).
> This has the benefit of:

Before you list the benefits, you should always talk about the lack of 
security! Let nobody enable it without realizing the dangers! Tell people 
to _only_ do this inside a company firewall, and even then, only if you 
trust everybody.

>   2) A less ugly URL to use: git://server/repo, instead of, say,
>      ssh+git://server/path/to/repos/repo.

Why do people use that silly "ssh+git://" format?

It's a cogito thing. Native git has never done it, and only supports it 
because cogito thought it must make sense.

The native git ssh URL is exactly the normal ssh URL:


and if you really want to use the "xxx://" format, you might as well just 


which should also work fine. 


PS. This is the commit message that  added "git+ssh://":

	Author: Linus Torvalds <>
	Date:   Fri Oct 14 17:14:56 2005 -0700
	    Support git+ssh:// and ssh+git:// URL
	    It seemed to be such a stupid syntax. It's both what "ssh://" means,
	    and it's what not specifying a protocol at _all_ means.
	    But hey, since we already have two ways of saying "use ssh with
	    pack-files", here's two more.

so it was deemed stupid from the get-go, and isn't even some "legacy" 
thing. It's purely a "cogito people thought it makes sense to point out 
that it's _both_ native git _and_ ssh protocol".

  reply	other threads:[~2007-02-14 16:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-14  3:14 Junio C Hamano
2007-02-14  9:06 ` Andy Parkins
2007-02-14  9:35   ` Junio C Hamano
2007-02-14  9:48     ` Junio C Hamano
2007-02-14 14:57 ` Bill Lear
2007-02-14 16:45   ` Linus Torvalds [this message]
2007-02-15  1:55 ` Jakub Narebski
2007-02-15  2:11   ` Shawn O. Pearce

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:

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

  git send-email \ \ \ \ \ \ \
    --subject='Re: [ANNOUNCE] GIT 1.5.0' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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