public inbox for qemu-devel@nongnu.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [PULL 0/6] Miscellaneous patches for 2026-03-05
Date: Fri, 06 Mar 2026 10:51:11 +0100	[thread overview]
Message-ID: <87ldg5i8vk.fsf@pond.sub.org> (raw)
In-Reply-To: <CAFEAcA8FLwV14q_nh3L6Cvw58ZnjfBBuG84ANAm5xDd=6zS5GQ@mail.gmail.com> (Peter Maydell's message of "Thu, 5 Mar 2026 16:58:37 +0000")

Peter Maydell <peter.maydell@linaro.org> writes:

> On Thu, 5 Mar 2026 at 14:05, Markus Armbruster <armbru@redhat.com> wrote:
>>
>> The following changes since commit 3fb456e9a0e9eef6a71d9b49bfff596a0f0046e9:
>>
>>   Merge tag 'pull-request-2026-03-02' of https://gitlab.com/thuth/qemu into staging (2026-03-02 14:01:46 +0000)
>>
>> are available in the Git repository at:
>>
>>   https://repo.or.cz/qemu/armbru.git tags/pull-misc-2026-03-05
>
> fetching from remote https://repo.or.cz/qemu/armbru.git
> tags/pull-misc-2026-03-05
> fatal: https://repo.or.cz/qemu/armbru.git/info/refs not valid: is this
> a git repository?
>
> Looking at it in a web browser:
>
>> The repo.or.cz site is no longer available in the UK.

https://repo.or.cz/uk-blocked.html

    repo.or.cz / site guide / UK geoblocking

    The repo.or.cz site is no longer available in the UK.

    We hate it as much as you do, but starting 25 July 2025, UK's Online
    Safety Act 2023 would require us to do a prohibitively complicated
    risk assessment for our service. We're talking reading through
    thousands of pages of legal guidelines.

    We're a volunteer operation and would likely be held responsible as
    individuals. There is talk of fines up to 18 million GBP which would
    ruin any single one of us, should they get creative about how to
    actually enforce this.

    Our impression is that this law is deliberately vague, deliberately
    drastic in its enforcement provisions, and specifically aimed
    against websites of all sizes, including hobby projects. In other
    words, this seems to us to be largely indistinguishable from an
    attempt to basically break the internet for all UK citizens.

    If we could afford to just hope for the best, we'd love to. After
    this, I know I will think twice about visiting the UK, but it's not
    like I can be completely certain that I will never have to...

    Our most sincere apologies to our UK-based users.

    For more details, see:

        https://howto.geoblockthe.uk/
        OnlineSafetyAct.co.uk (unofficial page)

To vary the famous motto of the Society for German–Soviet Friendship:
"Von der Volksrepublik China lernen heißt siegen lernen."

> If you want your pullreqs applied you'll need to find a different
> place to host them, I'm afraid.

Looks like it.



      reply	other threads:[~2026-03-06  9:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-05 14:05 [PULL 0/6] Miscellaneous patches for 2026-03-05 Markus Armbruster
2026-03-05 14:05 ` [PULL 1/6] hw/core: Deprecate query-kvm Markus Armbruster
2026-03-05 14:05 ` [PULL 2/6] scripts/checkpatch: Fix MAINTAINERS update warning with --terse Markus Armbruster
2026-03-05 14:05 ` [PULL 3/6] error: Fix "to current monitor if we have one" comments Markus Armbruster
2026-03-05 14:05 ` [PULL 4/6] error: Restore error_printf()'s function comment Markus Armbruster
2026-03-05 14:05 ` [PULL 5/6] qemu-print: Document qemu_fprintf(), qemu_vfprintf() failure Markus Armbruster
2026-03-05 14:05 ` [PULL 6/6] qdev-monitor: Fix qdev ID validation regression Markus Armbruster
2026-03-05 16:58 ` [PULL 0/6] Miscellaneous patches for 2026-03-05 Peter Maydell
2026-03-06  9:51   ` Markus Armbruster [this message]

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=87ldg5i8vk.fsf@pond.sub.org \
    --to=armbru@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.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