PRs for manpage 'grep(1)'
This is an experimental report containing PRs for manpage 'grep(1)' as of Fri May 30 07:37:23 2014 UTC. See notes.
PRs for manpage 'grep(1)':
S | Submitted | Tracker | Resp. | Description |
---|---|---|---|---|
o | 2013/08/13 | bin/181263 | grep(1) crashes at memchr/__sfvwrite when using colors | |
o | 2012/04/12 | bin/166862 | grep(1): grep [[:alnum:]]* only matches once | |
o | 2011/09/19 | bin/160834 | [patch] grep(1): fixes for POSIX conformance | |
o | 2011/04/28 | gnu/156704 | Improper behaviour of GNU grep(1) | |
o | 2010/12/13 | bin/153124 | grep(1): "grep foo * > somefile" goes into an infinite loop | |
o | 2010/07/31 | bin/149152 | gabor | [patch] grep(1): BSD grep loops with EISDIR trying to read a directory |
o | 2008/11/06 | gnu/128645 | [patch] grep(1): teach grep -r to how to ignore directories | |
o | 2007/06/04 | gnu/113343 | [patch] grep(1) outputs NOT-matched lines (with multi-bytes characters) | |
o | 2006/11/06 | gnu/105221 | grep(1): `grep -w -F ""` issue | |
o | 2006/08/20 | bin/102299 | [patch] grep(1) malloc abuse? |
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.