sourcehut first impression, share a repo seems not to work flawlessly

[Malcolm Matalka]

Uwe Brauer <oub at mat.ucm.es> writes:

>>>> "UB" == Uwe Brauer <oub at mat.ucm.es> writes:
>
>    > Hi
>
>    > I just opened two accounts
>
>
>
>    >     1. User 1 generated repo 1 and shared it with user2.
>
>    >     2. User 2 did not receive any email with any link, worse
>
>    >     3. User 2 does not see the shared repository.
>
>    > So far an essential feature seems not to work
>
> Ok I got it to work, but it is not very intuitive
> user 2 can in fact, clone, push and pull
> using
>
>  hg push  ssh://hg@hg.sr.ht/~user1/repo1
>
> In bitbucket user2 would have used
>
>  hg push  ssh://hg@hg.sr.ht/~user2/repo1

That's not quite true.  They would if they forked it, however if you
share a repo on bitbucket with someone and give them read/write access
to it, they would use the same URL as the owner of the
repository.

>
> And received an email with some explanations.
>
> More comments
>
>     1. Push, pull and clone seem to be considerable slower than for
>        bitbucket, because I pushed to both just now.
>
>     2. So far  I have really missed the https support.
>
> Uwe Brauer
> _______________________________________________
> Mercurial mailing list
> Mercurial at mercurial-scm.org
> https://www.mercurial-scm.org/mailman/listinfo/mercurial
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 487 bytes
Desc: not available
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20190821/ee5c6b1d/attachment.asc>