From: "simark at simark dot ca" <sourceware-bugzilla@sourceware.org>
To: overseers@sourceware.org
Subject: [Bug Infrastructure/30029] Please patch email-to-bugzilla to recognize Bug: trailer
Date: Fri, 20 Jan 2023 16:33:57 +0000 [thread overview]
Message-ID: <bug-30029-14326-jKQSUf6cBj@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30029-14326@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30029
Simon Marchi <simark at simark dot ca> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |simark at simark dot ca
--- Comment #1 from Simon Marchi <simark at simark dot ca> ---
I have shown interest in doing that. First converting the script to Python
(because I don't know Perl, and I think that less and less people do), as well
as adding simple regression tests, before adding more features. Joel sent me
current script, I will attach it.
I have started on December 3rd, according to the modification date, but haven't
touched it since. I will try to continue soon-ish, but if someone is motivated
to do it right now, I can send what I have now.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2023-01-20 16:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-20 16:29 [Bug Infrastructure/30029] New: " tromey at sourceware dot org
2023-01-20 16:33 ` simark at simark dot ca [this message]
2023-02-07 18:10 ` [Bug Infrastructure/30029] " tromey at sourceware dot org
2023-02-07 18:17 ` fche at redhat dot com
2023-02-07 19:15 ` mark at klomp dot org
2023-02-08 2:13 ` tromey at sourceware dot org
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=bug-30029-14326-jKQSUf6cBj@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=overseers@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).