All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	Petr Baudis <pasky@suse.cz>,
	git@vger.kernel.org
Cc: Martin Mares <mj@ucw.cz>, Sven Verdoolaege <skimo@liacs.nl>
Subject: Re: repo.or.cz wishes?
Date: Tue, 28 Aug 2007 01:16:00 +0200	[thread overview]
Message-ID: <200708280116.00537.jnareb@gmail.com> (raw)
In-Reply-To: <alpine.LFD.0.999.0708271509230.25853@woody.linux-foundation.org>

Linus Torvalds wrote:

> As to your TLS example: if we were to do "git over TLS", it would make 
> perfect sense to use either "tls://" (although "gits://" might be more 
> natural, not because tls is wrong, but because people have gotten used to 
> "https://") if we were to have a "secure git" port. Or maybe we'd use the 
> same port number that we already have assigned for git, and just add some 
> "use TLS to authenticate/encrypt", and use "tls://" for that. It makes 
> perfect sense.

I like gits:// idea for "git over TLS", and I'm against "tls://". I wonder
if it would be hard to implement "git overt TLS"? We could resurrect patch
which allowed push over git protocol, onnly restricting pushing to gits
protocol.

-- 
Jakub Narebski
Poland

  parent reply	other threads:[~2007-08-27 23:18 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
2007-08-27 23:30               ` Sam Vilain
2007-08-27 23:34                 ` Linus Torvalds
2007-08-27 23:16           ` Jakub Narebski [this message]
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=200708280116.00537.jnareb@gmail.com \
    --to=jnareb@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=mj@ucw.cz \
    --cc=pasky@suse.cz \
    --cc=skimo@liacs.nl \
    --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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.