public inbox for ecos-bugs@sourceware.org
help / color / mirror / Atom feed
From: bugzilla-daemon@ecoscentric.com
To: unassigned@bugs.ecos.sourceware.org
Subject: Your Issue Management System issue list needs attention.
Date: Wed, 01 Dec 2010 11:05:00 -0000	[thread overview]
Message-ID: <20101201005504.0FE4A2F7800C@mail.ecoscentric.com> (raw)

[This e-mail has been automatically generated.]

You have one or more issues assigned to you in the Issue Management System issue tracking system (http://bugzilla.ecoscentric.com/) that require
attention.

All of these issues are in the NEW or REOPENED state, and have not been
touched in 7 days or more.
You need to take a look at them, and decide on an initial action.

Generally, this means one of three things:

(1) You decide this issue is really quick to deal with (like, it's INVALID),
    and so you get rid of it immediately.
(2) You decide the issue doesn't belong to you, and you reassign it to
    someone else. (Hint: if you don't know who to reassign it to, make
    sure that the Component field seems reasonable, and then use the
    "Reset Assignee to default" option.)
(3) You decide the issue belongs to you, but you can't solve it this moment.
    Accept the issue by setting the status to ASSIGNED.

To get a list of all NEW/REOPENED issues, you can use this URL (bookmark
it if you like!):
http://bugzilla.ecoscentric.com/buglist.cgi?bug_status=NEW&bug_status=REOPENED&assigned_to=unassigned@bugs.ecos.sourceware.org

Or, you can use the general query page, at 
http://bugzilla.ecoscentric.com/query.cgi

Appended below are the individual URLs to get to all of your NEW issues
that haven't been touched for 7 days or more.

You will get this message once a day until you've dealt with these issues!

 Truncate tests for diag_snprintf()
    -> http://bugzilla.ecoscentric.com/show_bug.cgi?id=1001080


             reply	other threads:[~2010-12-01  0:55 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-01 11:05 bugzilla-daemon [this message]
2011-01-01  0:55 bugzilla-daemon
2011-02-01  0:55 bugzilla-daemon
2011-03-01  0:55 bugzilla-daemon
2011-03-31 23:55 bugzilla-daemon
2011-04-30 23:55 bugzilla-daemon
2011-05-31 23:55 bugzilla-daemon
2011-07-31 23:55 bugzilla-daemon
2011-08-31 23:55 bugzilla-daemon
2011-09-30 23:55 bugzilla-daemon
2011-11-01  0:55 bugzilla-daemon
2011-12-01  0:55 bugzilla-daemon
2012-01-01  0:55 bugzilla-daemon
2012-02-01  0:55 bugzilla-daemon
2012-03-01  0:55 bugzilla-daemon
2012-03-31 23:55 bugzilla-daemon
2012-04-30 23:55 bugzilla-daemon
2012-05-31 23:55 bugzilla-daemon
2012-06-30 23:55 bugzilla-daemon
2012-07-31 23:55 bugzilla-daemon
2012-08-31 23:55 bugzilla-daemon
2012-09-30 23:55 bugzilla-daemon
2012-11-01  0:55 bugzilla-daemon
2012-12-01  0:55 bugzilla-daemon
2013-01-01  0:55 bugzilla-daemon
2013-02-01  0:55 bugzilla-daemon

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=20101201005504.0FE4A2F7800C@mail.ecoscentric.com \
    --to=bugzilla-daemon@ecoscentric.com \
    --cc=unassigned@bugs.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).