#77 cloning via ssh doesn't list changes (differs from http, file)

Closed on November 27, 2020
robx on November 16, 2020

Not sure if listing the changes at all is desirable, but it’d be great if there was no difference between the various remotes. Currently, I see:

Local path:

$ pijul clone pijul pijul-clone
Applying "QJHXSKHHGRTAHN7MGYXPHWBEOTSXN63JJVIOI3OCIZTV5R6BCRSAC"
Applying "DBFB3VISVD3WBQKSSQCNMVCSYF3OTLPN4AGO4EWAZK4GFCPKA2BQC"
...
$ 

HTTP:

pijul clone https://nest.pijul.com/pijul/pijul pijul-http
Applying "QJHXSKHHGRTAHN7MGYXPHWBEOTSXN63JJVIOI3OCIZTV5R6BCRSAC"
Applying "DBFB3VISVD3WBQKSSQCNMVCSYF3OTLPN4AGO4EWAZK4GFCPKA2BQC"
...
$ 

SSH:

$ pijul clone robx@nest.pijul.com/pijul/pijul pijul-ssh
$ 
pmeunier on November 16, 2020

This actually comes from the fact that SSH doesn’t apply the changes, it clones the graph directly. This can be a big optimisation on large repositories. It isn’t implemented (yet) on local clones, and the Nest doesn’t yet respond to these URLs.

robx on November 16, 2020

I see, that makes sense. It’s a bit confusing from a UX perspective… I was used to http-clone being noisy, so I was surprised that a silent ssh clone actually worked. Maybe a log line “Cloning graph…” could be nice to show that something is happening? Or we just wait for local/http cloning to also be silent and this will all go away.

pmeunier on November 27, 2020

This is fixed by #Q45QHPO4HDTEZF2W4UDZSYYQ46BPEIWSW4GJILZR5HTJNLKXJABQC

Thanks for reporting!

pmeunier closed this discussion on November 27, 2020