New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Decouple nspr int types #2169

Closed

389-ds-bot opened this issue Sep 13, 2020 · 4 comments

Labels

closed: won't fix complex

Milestone

389-ds-bot commented Sep 13, 2020

Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/49110

Created at 2017-01-31 11:51:47 by firstyear (@Firstyear)
Closed at 2020-04-29 16:44:49 as wontfix
Assigned to firstyear (@Firstyear)

We should use the clear and portable inttypes.h if possible. This means removing int, long, long long, float, short, pruint and others.

389-ds-bot added closed: won't fix complex labels

389-ds-bot added this to the FUTURE milestone

389-ds-bot closed this as completed

Author

389-ds-bot commented Sep 13, 2020

Comment from firstyear (@Firstyear) at 2017-02-11 22:59:57

Metadata Update from @Firstyear:

Issue assigned to Firstyear
Issue set to the milestone: FUTURE

Author

389-ds-bot commented Sep 13, 2020

Comment from firstyear (@Firstyear) at 2017-03-10 01:47:05

Metadata Update from @Firstyear:

Issue close_status updated to: None
Issue tagged with: Complex

Author

389-ds-bot commented Sep 13, 2020

Comment from mreynolds (@mreynolds389) at 2020-04-29 16:44:50

We are working on this as we make fix and improvements. It will not be done in one phase, closing since this is on our radar.

Author

389-ds-bot commented Sep 13, 2020

Comment from mreynolds (@mreynolds389) at 2020-04-29 16:44:51

Metadata Update from @mreynolds389:

Custom field reviewstatus adjusted to None
Issue close_status updated to: wontfix
Issue status updated to: Closed (was: Open)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment