From: Torokhov Sergey <torokhov-s-a@yandex.ru>
To: "gentoo-dev@lists.gentoo.org" <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] Adding heptapod as new <remote-id> in metadata.dtd
Date: Wed, 14 Oct 2020 02:19:26 +0300 [thread overview]
Message-ID: <522451602630706@mail.yandex.ru> (raw)
In-Reply-To: <1492121602629943@mail.yandex.ru>
Excuse me for text/html in initial letter. I duplicate start message with text/plain below
without attachments as they are available on MARC:
>>>
Hello!
Due to recent sunset on mercurial support by Bitbucket [1]
the project early hosted there that uses mercurial vcs
have to migrate to other mercurial hosting.
One of them is new hosting heptapod [2] based on the Gitlab.
For free and open source project the service provides free of charge hosting [3].
E.g. the following projects migrate to heptapod:
Tortoisehg : https://foss.heptapod.net/mercurial/tortoisehg/thg
PyPy : https://foss.heptapod.net/pypy/pypy
The attached patches offer to add 'heptapod' (i.e. 'foss.heptapod.net' [3])
as new <remote-id> item to 'dtd/metadata.dtd' and to 'xml-schema/metadata.xsd'.
Then it could be used to set in 'matadata.xml' an additional info about :
for dev-python/pypy{,3}: <remote-id type="heptapod">pypy/pypy</remote-id>
for dev-vcs/tortoisehg: <remote-id type="heptapod">mercurial/tortoisehg/thg</remote-id>
[1] https://bitbucket.org/blog/sunsetting-mercurial-support-in-bitbucket
[2] https://heptapod.net
[3] https://foss.heptapod.net
--
Sergey Torokhov
<<<
next prev parent reply other threads:[~2020-10-13 23:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-13 23:02 [gentoo-dev] Adding heptapod as new <remote-id> in metadata.dtd Torokhov Sergey
2020-10-13 23:19 ` Torokhov Sergey [this message]
2020-10-14 6:59 ` Michał Górny
2020-10-15 18:14 ` Michał Górny
2020-10-15 22:19 ` Torokhov Sergey
2020-11-04 17:13 ` Torokhov Sergey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=522451602630706@mail.yandex.ru \
--to=torokhov-s-a@yandex.ru \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox