PRs for manpage 'tzsetup(8)'
This is an experimental report containing PRs for manpage 'tzsetup(8)' as of Fri May 25 07:44:14 2012 UTC. See notes.
PRs for manpage 'tzsetup(8)':
| S | Submitted | Tracker | Resp. | Description |
|---|---|---|---|---|
| o | 2012/02/11 | bin/164976 | dteske | [PATCH] tzsetup(8): Fix VERBOSE reporting on results when removing _PATH_LOCALTIME for UTC option |
| p | 2012/01/12 | bin/164042 | dteske | [PATCH] tzsetup(8): Fix VERBOSE to work with new UTC menu option |
| p | 2012/01/12 | bin/164041 | dteske | [PATCH] tzsetup(8): Remove unnecessary code duplication and clean-up reinstall option |
| p | 2012/01/12 | bin/164039 | dteske | [PATCH] tzsetup(8): Don't write /var/db/zoneinfo either when "-n" is passed or when install_zoneinfo_file returns failure |
| p | 2012/01/12 | bin/164038 | wollman | [PATCH] tzsetup(8): Increase buffer size to hold error messages |
| o | 2011/09/09 | bin/160596 | eadler | [patch] tzsetup(8): Use libodialog when doing tzsetup source upgrades from earlier versions of FreeBSD to 9.x post r217309 |
Notes
GNATS has no finer-grained categorization than 'kern', 'bin', 'ports', and so forth. To augment this, the bugmeisters have adopted the convention of adding '<name>(<section>)' to the Synopsis field. Consider this a prototype of a better search function.
Please give feedback on this report to linimon@FreeBSD.org. Thanks.
Bugs can be in one of several states:
- o - open
- A problem report has been submitted, no sanity checking performed.
- a - analyzed
- The problem is understood and a solution is being sought.
- f - feedback
- Further work requires additional information from the originator or the community - possibly confirmation of the effectiveness of a proposed solution.
- p - patched
- A patch has been committed, but some issues (MFC and / or confirmation from originator) are still open.
- r - repocopy
- The resolution of the problem report is dependent on a repocopy operation within the CVS repository which is awaiting completion.
- s - suspended
- The problem is not being worked on, due to lack of information or resources. This is a prime candidate for somebody who is looking for a project to do. If the problem cannot be solved at all, it will be closed, rather than suspended.
- c - closed
- A problem report is closed when any changes have been integrated, documented, and tested -- or when fixing the problem is abandoned.