From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: overseers@sourceware.org
Subject: [Bug Infrastructure/31529] binutils-cvs isn't updating on inbox.sourceware.org
Date: Tue, 09 Apr 2024 15:30:16 +0000 [thread overview]
Message-ID: <bug-31529-14326-gXXQQJFIog@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31529-14326@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=31529
--- Comment #1 from Mark Wielaard <mark at klomp dot org> ---
I assumed it was because the emails were sent to the alias, so I tried to
update the splitting script (also updating the components):
diff --git a/email_to.py b/email_to.py
index 8294028..dd54560 100755
--- a/email_to.py
+++ b/email_to.py
@@ -1,24 +1,27 @@
#! /usr/bin/env python
import sys
-ML_MAP = {'bfd': 'bfd-cvs@sourceware.org',
+ML_MAP = {'binutils': 'binutils-cvs@sourceware.org',
'gdb': 'gdb-cvs@sourceware.org',
}
OWNER_MAP = (
- # BFD file...
- ('bfd/', 'bfd'),
- ('binutils/', 'bfd'),
- ('opcode/', 'bfd'),
- ('cpu/', 'bfd'),
- ('elfcpp/', 'bfd'),
- ('gas/', 'bfd'),
- ('gold/', 'bfd'),
- ('gprof/', 'bfd'),
- ('include/', 'bfd'),
- ('ld/', 'bfd'),
- ('opcodes/', 'bfd'),
+ # BINUTILS file...
+ ('bfd/', 'binutils'),
+ ('binutils/', 'binutils'),
+ ('opcode/', 'binutils'),
+ ('cpu/', 'binutils'),
+ ('elfcpp/', 'binutils'),
+ ('gas/', 'binutils'),
+ ('gold/', 'binutils'),
+ ('gprof/', 'binutils'),
+ ('gprofng/', 'binutils'),
+ ('include/', 'binutils'),
+ ('ld/', 'binutils'),
+ ('opcodes/', 'binutils'),
+ ('libsframe/', 'binutils'),
+ ('libctf/', 'binutils'),
# GDB files...
('gdb/', 'gdb'),
('gdbserver/', 'gdb'),
But this doesn't seem to be it.
--
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2024-04-09 15:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-22 11:17 [Bug Infrastructure/31529] New: " mark at klomp dot org
2024-03-23 11:04 ` [Bug Infrastructure/31529] " sam at gentoo dot org
2024-04-09 15:30 ` mark at klomp dot org [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=bug-31529-14326-gXXQQJFIog@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).