You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It can be very difficult on users if the version of the manpage for SSSD they're looking at doesn't match the version installed on their machines. This can happen if they are looking at manpages on the web or on a different OS from the machine they are configuring.
It would be very useful if we could identify the SSSD version that an option was added in the manpages. This would make it easier to support multiple versions.
This would be nice upstream, but would get tricky for backports. We would have to make sure to always update the version when backporting a feature that includes a new option.
_comment0: This would be nice upstream, but would get tricky for rebases. We would have to make sure to always update the version when backporting a feature that includes a new option. => 1352200508292753
Thank you for taking time to submit this request for SSSD. Unfortunately this issue was not given priority and the team lacks the capacity to work on it at this time.
Given that we are unable to fulfill this request I am closing the issue as wontfix.
If the issue still persist on recent SSSD you can request re-consideration of this decision by reopening this issue. Please provide additional technical details about its importance to you.
Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/1618
It can be very difficult on users if the version of the manpage for SSSD they're looking at doesn't match the version installed on their machines. This can happen if they are looking at manpages on the web or on a different OS from the machine they are configuring.
It would be very useful if we could identify the SSSD version that an option was added in the manpages. This would make it easier to support multiple versions.
Comments
Comment from jhrozek at 2012-11-06 12:13:07
This would be nice upstream, but would get tricky for backports. We would have to make sure to always update the version when backporting a feature that includes a new option.
_comment0: This would be nice upstream, but would get tricky for rebases. We would have to make sure to always update the version when backporting a feature that includes a new option. => 1352200508292753
Comment from dpal at 2012-11-08 15:42:18
Fields changed
milestone: NEEDS_TRIAGE => SSSD Deferred
rhbz: => 0
Comment from dpal at 2012-11-08 15:43:23
We will publish doc changes on the wiki with every release.
Comment from sgallagh at 2017-02-24 15:07:25
Metadata Update from @sgallagh:
Comment from pbrezina at 2020-03-24 14:20:43
Thank you for taking time to submit this request for SSSD. Unfortunately this issue was not given priority and the team lacks the capacity to work on it at this time.
Given that we are unable to fulfill this request I am closing the issue as wontfix.
If the issue still persist on recent SSSD you can request re-consideration of this decision by reopening this issue. Please provide additional technical details about its importance to you.
Thank you for understanding.
Comment from pbrezina at 2020-03-24 14:20:44
Metadata Update from @pbrezina:
The text was updated successfully, but these errors were encountered: