From: "John Kacur" <jkacur@gmail.com>
To: "Jan Engelhardt" <jengelh@medozas.de>
Cc: "Andy Whitcroft" <apw@shadowen.org>,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: Make the git URL match usage
Date: Wed, 16 Jul 2008 14:30:52 +0200 [thread overview]
Message-ID: <520f0cf10807160530g1a9c3a09w2fd4237199612fd7@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.1.10.0807161338290.26724@fbirervta.pbzchgretzou.qr>
On Wed, Jul 16, 2008 at 1:43 PM, Jan Engelhardt <jengelh@medozas.de> wrote:
>
> On Wednesday 2008-07-16 12:34, John Kacur wrote:
>>>
>>> This now looses information. Although it is obvious that this particular
>>> example (after conversion) is a git repository over git protocol this falls
>>> down for other forms, for example a git repository exported over http://
> [...]
>
> git over http really is no fun at the moment and one should really
> use git:// whenever possible. Where it is not possible due to
> tightknotted corporate firewalls, well, that's (a) their problem and
> (b) they probably know already how to go around it.
>
> If in doubt, just add a paragraph that one can exchange git://
> by http://, but I would not make it that obvious to use an inferior
> transfer protocol.
>
Luckily I didn't see any use of http:// with git listed in the MAINTAINERS file.
next prev parent reply other threads:[~2008-07-16 12:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-16 8:47 jkacur
2008-07-16 10:21 ` Andy Whitcroft
2008-07-16 10:34 ` John Kacur
2008-07-16 11:43 ` Jan Engelhardt
2008-07-16 12:30 ` John Kacur [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-07-16 13:00 jkacur
2008-07-16 13:31 ` Adrian Bunk
2008-07-16 13:41 ` Mark Brown
2008-07-16 15:16 ` Jan Engelhardt
2008-07-16 13:53 ` Grant Likely
2008-07-16 13:54 ` Josh Boyer
[not found] <aQ9CN-4cK-11@gated-at.bofh.it>
2008-07-16 8:54 ` Bodo Eggert
2008-07-16 10:06 ` Jan Engelhardt
2008-07-16 10:28 ` John Kacur
2008-07-16 10:58 ` John Kacur
2008-07-16 7:19 jkacur
2008-07-16 8:29 ` Jan Engelhardt
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=520f0cf10807160530g1a9c3a09w2fd4237199612fd7@mail.gmail.com \
--to=jkacur@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=apw@shadowen.org \
--cc=jengelh@medozas.de \
--cc=linux-kernel@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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®