From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] New tool for updating Bug summaries after package moves: bugsed
Date: Thu, 12 Dec 2024 13:18:41 +0100 [thread overview]
Message-ID: <6cdc774b64cceb808e78bfe4f5b273f10d549480.camel@gentoo.org> (raw)
In-Reply-To: <02555bfc-1914-41fb-af0a-711118b0bb03@neuwirth-informatik.de>
[-- Attachment #1: Type: text/plain, Size: 552 bytes --]
On Thu, 2024-12-12 at 10:28 +0100, Alexander Neuwirth wrote:
> On 12/11/24 15:08, Michał Górny wrote:
> > you can quickly update
> > hundreds of bugs filed against it
>
> Does it need to be added to the list of exceptions [1] or is it
> considered as a manual, i.e. non-automated, script?
Well, I don't think it should really be considered a "bot", since it's
just a frontend script that does operations on your request. It's not
that different from "change multiple bugs" function in Bugzilla.
--
Best regards,
Michał Górny
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 512 bytes --]
prev parent reply other threads:[~2024-12-12 12:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 14:08 [gentoo-dev] New tool for updating Bug summaries after package moves: bugsed Michał Górny
2024-12-12 4:55 ` Sam James
2024-12-12 12:17 ` Michał Górny
2024-12-12 9:28 ` Alexander Neuwirth
2024-12-12 12:18 ` Michał Górny [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=6cdc774b64cceb808e78bfe4f5b273f10d549480.camel@gentoo.org \
--to=mgorny@gentoo.org \
--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