PRs for manpage 'sh(1)'
This is an experimental report containing PRs for manpage 'sh(1)' as of Sat Dec 7 07:39:04 2013 UTC. See notes.
PRs for manpage 'sh(1)':
|o||2013/08/20||bin/181435||sh(1) wait(1) builtin fails after bg job was SIG(STOP|TSTP|CONT) controlled|
|p||2013/03/13||standards/176916||jilles||[patch] sh(1): implement multiple arguments to wait builtin|
|o||2012/11/15||bin/173642||sh(1): ``here-document'' does not works in FreeBSD 9 /bin/sh|
|o||2012/09/07||bin/171427||sh(1): Hitting ^Z doesn't suspend jobs like expected|
|o||2012/08/15||bin/170651||On 9.0-RELEASE#0 and master sh(1) gobbles high bit at first|
|o||2012/06/10||docs/168915||doc||size of integers used by test(1) and sh(1) is not documented|
|p||2011/10/17||bin/161756||jilles||[patch] sh(1) /bin/sh: read files in 1024-byte chunks rather than 1023|
|o||2006/10/15||bin/104432||jilles||sh(1): remove undocumented "exp" and "let" builtins|
|o||2002/02/11||bin/34811||jilles||sh(1) "jobs" is not pipeable|
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.