git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: git@vger.kernel.org
Subject: dumb transports not being welcomed..
Date: Tue, 13 Sep 2005 14:07:58 -0700	[thread overview]
Message-ID: <7vek7s1xsh.fsf@assigned-by-dhcp.cox.net> (raw)

I've looked at ~80 git repositories publicly available at
kernel.org and noticed only 23 are prepared to handle dumb
transports.  That probably means either most of these trees are
not pulled by people without kernel.org accounts, or public are
using rsync or cogito to pull from these trees.  I somehow find
this number very discouraging ...

             reply	other threads:[~2005-09-13 21:08 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-13 21:07 Junio C Hamano [this message]
2005-09-13 21:14 ` dumb transports not being welcomed Sam Ravnborg
2005-09-13 21:30   ` Junio C Hamano
2005-09-13 21:42     ` Sam Ravnborg
2005-09-13 22:03     ` Horst von Brand
2005-09-13 22:23       ` Junio C Hamano
2005-09-13 22:11     ` Junio C Hamano
2005-09-13 22:21       ` Jeff Garzik
2005-09-13 22:29         ` Junio C Hamano
2005-09-14 13:21           ` Jeff Garzik
2005-09-13 22:29       ` Linus Torvalds
2005-09-13 22:37         ` Junio C Hamano
2005-09-13 22:55           ` Linus Torvalds
2005-09-13 23:02             ` Junio C Hamano
2005-09-14  2:25               ` Kay Sievers
2005-09-14  3:32                 ` Junio C Hamano
2005-09-14  0:01         ` Johannes Schindelin
2005-09-14  0:57           ` Linus Torvalds
2005-09-14  1:42             ` Linus Torvalds
2005-09-14  8:38             ` Johannes Schindelin
2005-09-14 15:07               ` Linus Torvalds
2005-09-15  9:17         ` Junio C Hamano
2005-09-14 10:45       ` Sven Verdoolaege
2005-09-14 16:14         ` Junio C Hamano
2005-09-14 14:10       ` Jon Loeliger
2005-09-14 19:00         ` Junio C Hamano
2005-09-14 19:13           ` Jon Loeliger

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=7vek7s1xsh.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=git@vger.kernel.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).