PRs for manpage 'tcsh(1)'
This is an experimental report containing PRs for manpage 'tcsh(1)' as of Fri May 30 07:39:43 2014 UTC. See notes.
PRs for manpage 'tcsh(1)':
| S | Submitted | Tracker | Resp. | Description |
|---|---|---|---|---|
| o | 2013/06/17 | bin/179630 | tcsh(1): nls catalog file has wrong character code(ja_JP.eucJP) | |
| o | 2013/06/11 | bin/179488 | wrong encoding of error messages in tcsh(1) | |
| o | 2010/08/06 | bin/149363 | tcsh(1) cause situation when ssh connection closed | |
| o | 2008/12/02 | bin/129378 | csh(1) / tcsh(1) loses foreground process group [regression] | |
| o | 2007/05/04 | bin/112408 | mp | [regression] tcsh(1): tcsh causes gdb to hang (regression in tcsh) |
| o | 2006/08/21 | bin/102357 | [patch] tcsh(1)/csh(1) jobs control: sometimes 'fg' command doesn't capture back the background process | |
| o | 2005/11/08 | bin/88655 | [patch] tcsh(1): /bin/tcsh ls-F : Floating exception (core dumped) |
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.