From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: overseers@sourceware.org
Subject: [Bug Infrastructure/31529] New: binutils-cvs isn't updating on inbox.sourceware.org
Date: Fri, 22 Mar 2024 11:17:13 +0000 [thread overview]
Message-ID: <bug-31529-14326@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=31529
Bug ID: 31529
Summary: binutils-cvs isn't updating on inbox.sourceware.org
Product: sourceware
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: Infrastructure
Assignee: overseers at sourceware dot org
Reporter: mark at klomp dot org
Target Milestone: ---
https://sourceware.org/pipermail/binutils-cvs/
also accepts emails to bfd-cvs@sourceware.org
but this is rejects by https://inbox.sourceware.org/binutils-cvs
so the archives are stale (since the original import)
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2024-03-22 11:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-22 11:17 mark at klomp dot org [this message]
2024-03-23 11:04 ` [Bug Infrastructure/31529] " sam at gentoo dot org
2024-04-09 15:30 ` mark at klomp 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-31529-14326@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).