PRs for manpage 'fdisk(8)'
This is an experimental report containing PRs for manpage 'fdisk(8)' as of Fri May 30 07:36:59 2014 UTC. See notes.
PRs for manpage 'fdisk(8)':
| S | Submitted | Tracker | Resp. | Description |
|---|---|---|---|---|
| o | 2012/04/17 | bin/167036 | ambigious output of fdisk(8) | |
| o | 2010/07/09 | bin/148471 | fdisk(8) prompts with negative partition size [regression] | |
| o | 2010/01/31 | bin/143389 | [2tb] [patch] fdisk(8) cannot handle above 1TB under i386 system. | |
| o | 2007/01/11 | bin/107829 | fs | [2TB] fdisk(8): invalid boundary checking in fdisk / wraps value of > 2TB filesystem. |
| o | 2005/12/08 | bin/90093 | geom | fdisk(8) incapable of altering in-core geometry |
| o | 2005/08/09 | bin/84705 | fdisk(8) program warning about sector number is misleading | |
| o | 2004/01/25 | bin/61890 | sysinstall | sysinstall(8): fdisk(8) uses incorrect calculations for disk geometry guessing and validation |
| o | 2002/07/15 | bin/40597 | [patch] add fdisk(8) ability of showing extended partition tables |
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.