Good. Would it make sense for us to have some greppable tag for this situation where something should be fixed in the following release?
On Fri, Jul 19, 2013 at 2:52 AM, Sebastian Huber <[email protected]> wrote: > --- > cpukit/score/include/rtems/score/basedefs.h | 7 +++++++ > 1 files changed, 7 insertions(+), 0 deletions(-) > > diff --git a/cpukit/score/include/rtems/score/basedefs.h > b/cpukit/score/include/rtems/score/basedefs.h > index ebefe14..957b424 100644 > --- a/cpukit/score/include/rtems/score/basedefs.h > +++ b/cpukit/score/include/rtems/score/basedefs.h > @@ -33,6 +33,13 @@ > #include <stddef.h> > #include <stdbool.h> > #include <stdint.h> > + > + /* > + * This include should not be present. In older RTEMS versions <rtems.h> > + * provided <limits.h> indirectly. This include is here to not break > + * application source files that relied on this accidentally. > + */ > + #include <limits.h> > #endif > > #ifndef TRUE > -- > 1.7.7 > > _______________________________________________ > rtems-devel mailing list > [email protected] > http://www.rtems.org/mailman/listinfo/rtems-devel _______________________________________________ rtems-devel mailing list [email protected] http://www.rtems.org/mailman/listinfo/rtems-devel
