#3489 closed task (fixed)
Obsolete CONFIGURE_HAS_OWN_CONFIGURATION_TABLE
Reported by: | Sebastian Huber | Owned by: | Sebastian Huber |
---|---|---|---|
Priority: | normal | Milestone: | 5.1 |
Component: | config | Version: | 5 |
Severity: | normal | Keywords: | qualification |
Cc: | Blocked By: | ||
Blocking: | #3490 |
Description
Obsolete the CONFIGURE_HAS_OWN_CONFIGURATION_TABLE configuration option. The RTEMS configuration should be done via explicit configuration options to allow more freedom for implementation changes.
Change History (9)
comment:1 Changed on 08/08/18 at 07:14:19 by Sebastian Huber
Blocking: | 3490 added |
---|
comment:2 Changed on 08/08/18 at 07:28:53 by Chris Johns
comment:3 follow-up: 4 Changed on 08/08/18 at 07:30:23 by Sebastian Huber
Normally, I would say that we should deprecate it, however, it is broken since RTEMS 4.11 and we didn't get a bug report or complaint. There is also no test case for this configuration option.
comment:4 Changed on 08/08/18 at 07:31:47 by Sebastian Huber
Replying to Sebastian Huber:
Normally, I would say that we should deprecate it, however, it is broken since RTEMS 4.11 and we didn't get a bug report or complaint. There is also no test case for this configuration option.
Sorry, I answered to the wrong ticket.
Obsolete == deprecate? Next step is remove in 6.1 (#3490).
comment:5 Changed on 08/08/18 at 07:37:57 by Chris Johns
Thank you. Anyone interested can now see the reason.
comment:6 Changed on 08/08/18 at 07:41:30 by Sebastian Huber
Sorry, I added some confusion. The reason for this change is in the ticket description. Maybe I should delete this comment:
comment:8 Changed on 09/19/18 at 08:53:20 by Sebastian Huber <sebastian.huber@…>
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
comment:9 Changed on 06/23/21 at 07:16:03 by Sebastian Huber
Keywords: | qualification added |
---|
Should this be deprecated for a release before being removed?
Maybe the question should be asked on the user and devel lists if there are users?