From: "Frank Ch. Eigler" <fche@elastic.org>
To: Matthias Klose <doko@ubuntu.com>
Cc: "Frank Ch. Eigler" <fche@redhat.com>,
Gaius Mulley <gaius.mulley@southwales.ac.uk>,
overseers@sourceware.org
Subject: Re: SC question: adding a modula-2 (m2) component in the bug tracker?
Date: Mon, 30 Sep 2019 12:36:00 -0000 [thread overview]
Message-ID: <20190930123605.GA3764@elastic.org> (raw)
In-Reply-To: <6fc13335-a01f-c964-9776-00c1a97de956@ubuntu.com>
Hi -
> I approached you about that at the GNU Cauldron, and I'm now following up on
> that. David Edelsohn form SC told me that no approval from the SC would be
> needed to add a new category to the bug tracker.
Already done.
- FChE
next prev parent reply other threads:[~2019-09-30 12:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f57854da-9e82-c46e-983d-09d526696478@ubuntu.com>
2019-09-30 12:35 ` Matthias Klose
2019-09-30 12:36 ` Frank Ch. Eigler [this message]
2019-09-30 13:52 ` Gaius Mulley
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=20190930123605.GA3764@elastic.org \
--to=fche@elastic.org \
--cc=doko@ubuntu.com \
--cc=fche@redhat.com \
--cc=gaius.mulley@southwales.ac.uk \
--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).