PRs for manpage 'calendar(1)'
This is an experimental report containing PRs for manpage 'calendar(1)' as of Thu Apr 17 07:36:22 2014 UTC. See notes.
PRs for manpage 'calendar(1)':
|p||2014/02/12||bin/186697||eadler||calendar(1): -A -B -t not working correctly|
|o||2014/01/31||bin/186294||calendar(1): calendar' preprocessor process comments|
|o||2012/12/26||bin/174715||[patch] calendar(1): define Content-Type / charset when sending periodic mails|
|o||2012/08/23||bin/170930||edwin||calendar(1) core dumps with minor input format deviations|
|o||2012/06/07||bin/168785||calendar(1): /usr/bin/calendar does not match "Thu+1" or "Mon+1" in some months [regression]|
|o||2012/03/16||bin/166181||[patch] calendar(1): calendar -a does not work|
|o||2011/06/11||bin/157748||calendar(1): Patch for src/usr.bin/calendar/calendars/calendar.holiday|
|p||2011/06/08||bin/157718||edwin||input data trigers a core dump from calendar(1) [regression]|
|p||2011/03/22||bin/155873||edwin||calendar(1) recurring date not working|
|f||2003/03/19||bin/50118||edwin||calendar(1) dumps core if there is ./calendar/|
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.