Notice: We have migrated to GitLab launching 2024-05-01 see here: https://gitlab.rtems.org/

#60 closed enhancement (fixed)

GNATS: Additional state

Reported by: Ralf Corsepius Owned by: Jeff Mayes
Priority: lowest Milestone: 2
Component: admin Version: unknown
Severity: minor Keywords:
Cc: bugs@…, joel.sherrill@… Blocked By:
Blocking:

Description

I am missing a state in GNATS to denote that a problems is being worked at, eg. something like "locked", "taken", "busy" or similar.

In my understanding, none of the states currently being used is suiteable for this purpose.
Eg. I am currently working on fixing the simsh problem (bsps/45) and know this it will take some time.

Release:
NA

Change History (2)

comment:1 Changed on 10/30/01 at 21:25:44 by Jeff Mayes

Status: assignedclosed

State-Changed-From-To: open->closed
State-Changed-Why: Added the state "working" to denote that someone is actively seeking to solve the problem.

The states file needs to be formatted as follows:
state::description

comment:2 Changed on 01/15/24 at 09:37:51 by Tyler Miller <tyler.miller@…>

In [changeset:"2bbacdb557c74a513ecc6f3b2f581ac6b6344c4e/rtems" 2bbacdb/rtems]:

bsp/tms570: TMS570LC4x Errata DEVICE#60

Update #4982.

Note: See TracTickets for help on using tickets.