PRs for manpage 'fetch(1)'
This is an experimental report containing PRs for manpage 'fetch(1)' as of Fri Mar 7 07:36:52 2014 UTC. See notes.
PRs for manpage 'fetch(1)':
|o||2013/03/06||bin/176697||incorrect fetch(1) exit codes with -s option versus ftp proxy use|
|o||2011/06/01||bin/157499||fetch(1) confused me with its error message|
|o||2009/02/05||bin/131427||[patch] Add to fetch(1) an ability to limit a number of auto-retries|
|s||2007/12/31||bin/119196||des||fetch(1): [request] parallel download from multiple servers by fetch|
|o||2005/11/22||bin/89403||fetch(1) doesn't honour authentication credentials when going through a proxy|
|o||2005/01/12||bin/76134||fetch(1) doesn't like 401 errors with -A|
|s||2003/03/06||bin/48962||des||[patch] modify fetch(1) to allow bandwidth limiting|
|o||2002/09/24||bin/43337||des||[patch] fetch(1) -s fails if -4 or possibly other options given; inappropraite exit code if file does not exist on server|
|o||2001/04/23||bin/26803||fetch(1) Fix fetch to allow FTP puts in '-o' & allow '@' sign in URL|
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.