From: Mark Wielaard <mark@klomp.org>
To: Overseers mailing list <overseers@sourceware.org>
Cc: "Frank Ch. Eigler" <fche@elastic.org>,
"Jose E. Marchesi" <jemarch@gnu.org>
Subject: Re: Using sourceware's bugzilla for GNU poke
Date: Sat, 14 Nov 2020 18:40:05 +0100 [thread overview]
Message-ID: <20201114174005.GB3574@wildebeest.org> (raw)
In-Reply-To: <875z682d81.fsf@gnu.org>
Hi Jose,
On Sat, Nov 14, 2020 at 04:02:38PM +0100, Jose E. Marchesi via Overseers wrote:
> Would it be possible to have the following Components for the product
> `poke' in the sourceware bugzilla?
>
> Build (The build system)
> Compiler (The PKL compiler)
> RAS (Our dear Retarded Assembler)
> PVM (The Poke Virtual Machine)
> Runtime (Poke standard library and other runtime stuff)
> Library (Libpoke)
> MI (The Machine Interface)
> Emacs (Emacs related stuff, poke.el, poke-mode.el, etc)
> IO (The IO subsystem)
> POKE (poke, the program)
> CLI (Commands and interface)
> Pickles (Everything under pickles/)
> Documentation (The manual and other docs)
> Testsuite (Everything under testsuite/)
> GUI (Everything under gui/)
> Other (Kitchen sink)
I added your sourceware bugzilla user to the editcomponents group
which should allow you to manage the components of poke yourself at:
https://sourceware.org/bugzilla/editcomponents.cgi?product=poke
Cheers,
Mark
next prev parent reply other threads:[~2020-11-14 17:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-11 15:48 Jose E. Marchesi
2020-01-11 15:54 ` Frank Ch. Eigler
2020-01-11 16:56 ` Jose E. Marchesi
2020-01-11 18:23 ` Frank Ch. Eigler
2020-01-11 21:54 ` Jose E. Marchesi
2020-01-11 21:56 ` Frank Ch. Eigler
2020-01-12 9:33 ` Jose E. Marchesi
2020-01-16 21:58 ` Jose E. Marchesi
2020-01-16 22:16 ` Frank Ch. Eigler
2020-01-16 22:18 ` Jose E. Marchesi
2020-11-14 15:02 ` Jose E. Marchesi
2020-11-14 17:40 ` Mark Wielaard [this message]
2020-11-14 18:19 ` Jose E. Marchesi
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=20201114174005.GB3574@wildebeest.org \
--to=mark@klomp.org \
--cc=fche@elastic.org \
--cc=jemarch@gnu.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).