PRs for manpage 'sh(1)'
This is an experimental report containing PRs for manpage 'sh(1)' as of Fri May 25 07:43:26 2012 UTC. See notes.
PRs for manpage 'sh(1)':
| S | Submitted | Tracker | Resp. | Description |
|---|---|---|---|---|
| o | 2012/04/09 | bin/166771 | jilles | sh(1): "local var=$(cat)" only reads one line |
| p | 2011/10/17 | bin/161756 | jilles | [patch] sh(1) /bin/sh: read files in 1024-byte chunks rather than 1023 |
| o | 2011/06/23 | bin/158206 | jilles | sh(1) doesn't properly return IO errors to conditionals in a script |
| p | 2007/10/02 | standards/116826 | jilles | [patch] sh(1) support for POSIX character classes |
| o | 2006/10/15 | bin/104432 | jilles | sh(1): remove undocumented "exp" and "let" builtins |
| p | 2003/04/03 | bin/50569 | jilles | sh(1) doesn't handles ${HOME}/.profile correctly |
| o | 2002/02/11 | bin/34811 | jilles | sh(1) "jobs" is not pipeable |
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.