PRs for manpage 'bsdgrep(1)'
This is an experimental report containing PRs for manpage 'bsdgrep(1)' as of Fri May 30 07:36:19 2014 UTC. See notes.
PRs for manpage 'bsdgrep(1)':
| S | Submitted | Tracker | Resp. | Description |
|---|---|---|---|---|
| o | 2014/02/18 | bin/186861 | bsdgrep(1): xzgrep(1) sometimes doesn't find matches it should find | |
| o | 2013/12/12 | bin/184733 | bsdgrep(1) doesn't match a regular expression containing "|" against UTF-16 file [regression] | |
| o | 2013/08/01 | bin/180990 | bsdgrep(1) segfaults when pattern file contains many lines | |
| o | 2013/01/15 | bin/175314 | [regression] bsdgrep(1) broken multidot escaping since r225435 | |
| o | 2013/01/11 | bin/175213 | markj | [patch] bsdgrep(1) segfaults upon malicious input |
| f | 2012/08/31 | docs/171200 | issyl0 | the bsdgrep(1) man page should document -u |
| a | 2012/05/15 | bin/167921 | gabor | bsdgrep(1) segfaults with "\\." |
| o | 2012/04/11 | bin/166861 | bsdgrep(1)/sed(1): bsdgrep -E and sed handle invalid {} constructs strangely | |
| o | 2012/04/11 | bin/166842 | bsdgrep(1) inconsistently handles ^ in non-anchoring positions | |
| o | 2012/02/25 | bin/165471 | bsdgrep(1) hang/very slow with mmap |
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.