All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Thomas Huth <thuth@redhat.com>
Cc: qemu-devel@nongnu.org,  pbonzini@redhat.com
Subject: Re: [qemu-web RFC PATCH] blog post: some notes on the bugpocolypse
Date: Fri, 18 Sep 2026 16:43:59 +0100	[thread overview]
Message-ID: <87mrte5zuo.fsf@draig.linaro.org> (raw)
In-Reply-To: <10111cde-7d2e-4e81-8233-4ae940a95dac@redhat.com> (Thomas Huth's message of "Thu, 17 Sep 2026 11:10:07 +0200")

Thomas Huth <thuth@redhat.com> writes:

> On 11/09/2026 19.34, Alex Bennée wrote:
>> As we've been going throw the growing pains of AI bug bots I thought
>> it might be worth addressing in a blog post. I'm mainly just trying to
>> outline the challenges and maybe dissuade people from spam bombing the
>> bug tracker with lots of low value bugs in the more dusty corners of
>> the code base.
>> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
>> ---
>
>  Hi Alex,
>
> I was hoping that some native speaker would chime in first, but since
> nobody replied yet so far, let me try to provide some feedback:

I think non-native speakers are well placed to review blog posts because
helps make sure I don't introduce too many English colloquiums which
make the text less accessible.

With that in mind:

  Message-ID: <20260918141937.334849-1-alex.bennee@linaro.org>
  Date: Fri, 18 Sep 2026 15:19:37 +0100
  Subject: [qemu-web PATCH v2] blog post: some notes on the bugpocolypse
  From: =?UTF-8?q?Alex=20Benn=C3=A9e?= <alex.bennee@linaro.org>

;-)

-- 
Alex Bennée
Virtualisation Tech Lead @ Linaro


      parent reply	other threads:[~2026-09-18 15:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-11 17:34 [qemu-web RFC PATCH] blog post: some notes on the bugpocolypse Alex Bennée
2026-09-17  9:03 ` Alex Bennée
2026-09-17  9:10 ` Thomas Huth
2026-09-17 10:08   ` Alex Bennée
2026-09-18 15:43   ` Alex Bennée [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=87mrte5zuo.fsf@draig.linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.