From: Jeff Garzik <jgarzik@pobox.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Linus Torvalds <torvalds@osdl.org>, git@vger.kernel.org
Subject: Re: 2.6.15-rc2 tag
Date: Tue, 22 Nov 2005 15:38:52 -0500 [thread overview]
Message-ID: <20051122203852.GA15811@havoc.gtf.org> (raw)
In-Reply-To: <20051122201726.GB8738@fieldses.org>
On Tue, Nov 22, 2005 at 03:17:26PM -0500, J. Bruce Fields wrote:
> Yup, thanks. Is there any reason to ever use http to get to your
> repository?
Linus's? For you? Probably not. But for others:
1) Corporate firewalls, which only allow HTTP transit, without
jumping through hoops.
2) Far easier to find HTTP hosting than rsync or git hosting.
Jeff
next prev parent reply other threads:[~2005-11-22 20:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-21 21:25 2.6.15-rc2 tag J. Bruce Fields
2005-11-22 19:34 ` J. Bruce Fields
2005-11-22 20:01 ` Linus Torvalds
2005-11-22 20:17 ` J. Bruce Fields
2005-11-22 20:38 ` Jeff Garzik [this message]
2005-11-22 20:33 ` Junio C Hamano
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=20051122203852.GA15811@havoc.gtf.org \
--to=jgarzik@pobox.com \
--cc=bfields@fieldses.org \
--cc=git@vger.kernel.org \
--cc=torvalds@osdl.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 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).