From: Grant Edwards <grant.b.edwards@gmail.com>
To: ecos-devel@ecos.sourceware.org
Subject: Process for bugs fixed?
Date: Mon, 20 Jan 2014 15:24:00 -0000 [thread overview]
Message-ID: <lbjf2b$63b$1@ger.gmane.org> (raw)
Last week I ran across a bug in the BSD network stack which has had a
fix sitting in Bugzilla for a year and a half.
Are we still using Bugzilla?
Changes to bugs used to show up on the patches mailing list, but that
seems to have stopped happening last year.
What is the process for getting a bug fixed?
--
Grant Edwards grant.b.edwards Yow! World War III?
at No thanks!
gmail.com
reply other threads:[~2014-01-20 15:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='lbjf2b$63b$1@ger.gmane.org' \
--to=grant.b.edwards@gmail.com \
--cc=ecos-devel@ecos.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).