Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michael S. Zick <minimod@morethan.org>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC:bugzilla] Addition of Category "Test Report"
Date: Sat, 5 Dec 2009 02:59:22 -0600	[thread overview]
Message-ID: <200912050259.25672.minimod@morethan.org> (raw)

Would someone please add the category "test report" to "Severity"?

There is an unlikely but still small chance it might get used.
It certainly will not get used if it isn't there.  ;)

Example situation:

The MIPS core M14K<qualifier>, first documented in July, 2009 is not 
mentioned in the pre-release documentation for GCC-4.5 nor is the 
feature (microMIPS) first mentioned in the core's documentation.

The only way to find out the current status will be to build
the gcc-snapshot from time to time and check it for specific
support of the core.

For the moment (not yet tested the snapshot) the user-visible comment
will have to say "gcc support not determined REF: <something>"
It would be nice to have a bugzilla tracking number to put in the <something>.

Mike

                 reply	other threads:[~2009-12-05  8:59 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=200912050259.25672.minimod@morethan.org \
    --to=minimod@morethan.org \
    --cc=buildroot@busybox.net \
    /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