Skip site navigation (1)Skip section navigation (2)

Site Navigation

PRs for manpage 'mtree(8)'

This is an experimental report containing PRs for manpage 'mtree(8)' as of Sat Apr 19 07:38:08 2014 UTC. See notes.


PRs for manpage 'mtree(8)':
SSubmittedTrackerResp.Description
o2014/03/22bin/187838imp[patch] Add support for mtree(8) to populate_data_slice and cust_install_files, unify variable names.
o2013/08/29bin/181636mtree(8): mtree -U does not fix ownership of symbolic links
o2010/02/10bin/143732[patch] mtree(8) does a full hierarchy walk when requested to just update structure (-u -e)
o2003/04/14bin/50949mtree(8) doesn't honor the -P when checking/changing ownership
o2002/08/12bin/41583[patch] mtree(8) assorted mtree bugs
o2001/06/26bin/28424brooksmtree(8) fails to report directory hierarchy mismatch
6 problems total.


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.