pushkeys used? https://www.selenic.com/blog/?p=644

[Uwe Brauer]

> On 11/9/19 10:05 AM, Uwe Brauer wrote:


> I you are looking for a place migrate from bitbucket I recomment you
> look into the currently recommend option here: 
> https://www.mercurial-scm.org/wiki/MercurialHosting/#Comparison_table_with_Mercurial-specific_features


Thanks, I see Helix is  not there. It is free up to 5 users for the
moment, as a gui similar to bitbucket (but is a bit more difficult to
configure). I have not tried out its issues feature, but soon I will.


> namespaces is not a feature, it is an implementation details of
> pushkey to list the supported pushkey namespace.

Ok. 


So if it is not supported by a specific git conversion tool, what does
this mean for the the everyday workflow?

By everyday workflow I mean: the bitbucket mercurial repository is
converted to become a git repository with that specific conversion
tools, however all users push and pull using mercurial and the hg-git
extension.[1]

If the pushkey namespace was not supported during the conversion, what
is lost?

Footnotes:
[1]  the hg-git extension can be used to convert the mercurial
     repository to a git repository, however, meta-data such as issues
     are not converted.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5025 bytes
Desc: not available
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20191113/76156c6b/attachment.p7s>