On 7/29/2017 4:40 AM, Paul Moore wrote:
On 28 July 2017 at 23:30, Mariatta Wijaya wrote:
1. Section 32.2 in the Git bootcamp section - is there any reason to
use git@github URLs for the clones? I normally always use
https://github.com URLs, as they work with my proxy at work.
As I understand
On 29 July 2017 at 14:13, Nick Coghlan wrote:
> To be honest, the read-only=HTTPS & read/write=SSH split is likely a
> Linux+macOS-ism, where we can do "ssh-add" once, and then never have
> to worry about explicitly authenticating again until we reboot our
> client machine. As Inada-san notes, the
On 29 July 2017 at 18:40, Paul Moore wrote:
> On 28 July 2017 at 23:30, Mariatta Wijaya wrote:
>>> 1. Section 32.2 in the Git bootcamp section - is there any reason to
>>> use git@github URLs for the clones? I normally always use
>>> https://github.com URLs, as they work with my proxy at work.
>>
On 28 July 2017 at 23:30, Mariatta Wijaya wrote:
>> 1. Section 32.2 in the Git bootcamp section - is there any reason to
>> use git@github URLs for the clones? I normally always use
>> https://github.com URLs, as they work with my proxy at work.
>
>
> I don't have any explanation other than Git bo
