On 2012-03-19, Kris Craig <[email protected]> wrote:
> --f46d043892b5b345eb04bb9cfe02
> Content-Type: text/plain; charset=ISO-8859-1
>
> Hey Chris,
>
> On Mon, Mar 19, 2012 at 11:40 AM, Christopher Jones <
> [email protected]> wrote:
> I sense your hostility but I think you misunderstood my question. The
> workflow page currently recommends the "git:" one for cloning (which
> doesn't work for me, either). I think it should be changed to "https://",
> and I fully intend on making the change myself but first I wanted to ask
> here to make sure there wasn't a reason why they went with "git:" instead
> (i.e. I don't want to step on anybody's toes).
git:// is recommended when you can use it. The access is limited due to
port limiations, but the protocl itself is superior to https for
the purpose.
http is a fallback when you cannot use ssh (developers only) or git