public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: John Dallaway <john@dallaway.org.uk>
To: ecos-maintainers@ecos.sourceware.org
Subject: Bug crunching
Date: Sun, 22 Feb 2009 15:11:00 -0000	[thread overview]
Message-ID: <49A16B19.2080505@dallaway.org.uk> (raw)

eCos maintainers

We already have several bug reports against eCos 3.0 beta 1:

http://bugs.ecos.sourceware.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=eCos&version=3.0beta1&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&deadlinefrom=&deadlineto=&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=

I'm not complaining. The whole point of the beta period is to find and
eradicate bugs.

It would be helpful to share the load of processing these bugs as far as
possible. Could I therefore suggest that we all subscribe to the
"ecos-bugs" list on sourceware.org so that we are made aware of new bugs
as they arrive and can contribute where appropriate. Subscribing is
easily achieved using the mailing list request form:

  http://sourceware.org/lists.html#ml-requestor

Thank you

John Dallaway

             reply	other threads:[~2009-02-22 15:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-22 15:11 John Dallaway [this message]
2009-02-27 10:08 John Dallaway

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=49A16B19.2080505@dallaway.org.uk \
    --to=john@dallaway.org.uk \
    --cc=ecos-maintainers@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).