Skip site navigation (1)Skip section navigation (2)

Site Navigation

PRs for manpage 'fetch(1)'

This is an experimental report containing PRs for manpage 'fetch(1)' as of Thu Apr 17 07:36:56 2014 UTC. See notes.


PRs for manpage 'fetch(1)':
SSubmittedTrackerResp.Description
o2013/03/06bin/176697incorrect fetch(1) exit codes with -s option versus ftp proxy use
o2011/06/01bin/157499fetch(1) confused me with its error message
o2009/02/05bin/131427[patch] Add to fetch(1) an ability to limit a number of auto-retries
s2007/12/31bin/119196desfetch(1): [request] parallel download from multiple servers by fetch
o2005/11/22bin/89403fetch(1) doesn't honour authentication credentials when going through a proxy
o2005/01/12bin/76134fetch(1) doesn't like 401 errors with -A
s2003/03/06bin/48962des[patch] modify fetch(1) to allow bandwidth limiting
o2002/09/24bin/43337des[patch] fetch(1) -s fails if -4 or possibly other options given; inappropraite exit code if file does not exist on server
o2001/04/23bin/26803fetch(1) Fix fetch to allow FTP puts in '-o' & allow '@' sign in URL
9 problems total.


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.