From: jemarch@gnu.org (Jose E. Marchesi)
To: "Frank Ch. Eigler" <fche@elastic.org>
Cc: "Frank Ch. Eigler" <fche@redhat.com>, overseers@sourceware.org
Subject: Re: Using sourceware's bugzilla for GNU poke
Date: Sun, 12 Jan 2020 09:33:00 -0000 [thread overview]
Message-ID: <87eew53tpe.fsf@gnu.org> (raw)
In-Reply-To: <20200111215611.GH89021@elastic.org> (Frank Ch. Eigler's message of "Sat, 11 Jan 2020 16:56:11 -0500")
> I have created an account poke-devel@nongnu.org [...]
> How to set it?
(It's an admin operation.) Done.
Thanks! It works :)
next prev parent reply other threads:[~2020-01-12 9:33 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 [this message]
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
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=87eew53tpe.fsf@gnu.org \
--to=jemarch@gnu.org \
--cc=fche@elastic.org \
--cc=fche@redhat.com \
--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).