Re: disabling mercurial repositories

[Jan Beulich <jbeulich@xxxxxxxx>]

On 22.06.2022 10:47, Andrew Cooper wrote:
> On 22/06/2022 09:41, Jan Beulich wrote:
>> On 21.06.2022 15:48, Roger Pau Monné wrote:
>>> Last week we had a bit of an emergency when a web crawler started
>>> indexing all our mercurial repositories on xenbits, as caused the load
>>> on xenbits to go beyond what it can handle.
>>>
>>> As a temporary solution we decided to remove access to mercurial
>>> repositories, but the contents there are AFAIK only for historical
>>> repositories, so we might consider completely removing access to
>>> mercurial repositories.  This would however require migrating any
>>> repository we care about to git.
>>>
>>> I would like an opinion from committers as well as the broad community
>>> whether shutting down mercurial repositories and migrating whatever we
>>> care about is appropriate.  Otherwise we will need to implement some
>>> throttling to mercurial accesses in order to avoid overloading
>>> xenbits.
>> While I wouldn't strictly mind its shutting off or the disabling of
>> hgweb as was suggested in a reply, either would mean to me personally
>> that it wouldn't be easy enough anymore to warrant trying to hunt
>> down the origin of certain Linux side aspects in the 2.6.18-xen tree.
>> Admittedly me doing so has become increasingly rare over time ...
> 
> We could convert that into a git repo (probably a branch on an existing
> Linux.git to save most of the conversion work) and make it available via
> gitweb if it's still useful?

If such a conversion would go cleanly enough, why not.

Jan