Hey Chris,
On Mon, Mar 19, 2012 at 11:40 AM, Christopher Jones <
[email protected]> wrote:
>
>
> On 03/19/2012 11:34 AM, Kris Craig wrote:
>
> I noticed that the workflow page recommends using the SSH URL for cloning.
>> However, isn't that one much more limited access? I.e. for myself at
>> least, it just prompts for a password (presumably for the SSH "git" user)
>> which of course I don't have. Is there a reason why that's recommended or
>> is it just a typo? If the latter, I'd be inclined to change it to the SSL
>> (i.e. https) URL (which the FAQ recommends for clone/push and utilizes
>> php.net credentials) to minimize confusion.
>>
>>
> Which exact bit are you talking about, and did you check the page commit
> history?
>
> I added https:// because git: is not usable from where I am.
>
> I believe from your emails you have more git experience than me, and I
> know you've been asked several times to contribute to the docs: go do it.
>
> Chris
>
>
>
> --
> Email: [email protected]
> Tel: +1 650 506 8630
> Blog: http://blogs.oracle.com/opal/
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
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).
If nobody objects then yeah I'll gladly update it myself. =)
--Kris