| Summary: | libfetch-based fetch(1) has no useful -v output | ||
|---|---|---|---|
| Product: | Base System | Reporter: | Bill Fenner <fenner> |
| Component: | bin | Assignee: | Dag-Erling Smørgrav <des> |
| Status: | Closed FIXED | ||
| Severity: | Affects Only Me | ||
| Priority: | Normal | ||
| Version: | 5.0-CURRENT | ||
| Hardware: | Any | ||
| OS: | Any | ||
|
Description
Bill Fenner
2001-12-08 19:10:01 UTC
Responsible Changed From-To: freebsd-bugs->des I wrote libfetch. Bill Fenner <fenner@research.att.com> writes: > libfetch-based fetch(1) has no useful -v output. The old fetch(1) > printed out each command, so that you could see which one failed, libfetch does this if you build it with -DDEBUG. The output it produces is very verbose, though - quite possibly more verbose than you might like. DES -- Dag-Erling Smorgrav - des@ofug.org Well, consider this a feature request, then, to add a reasonable level of output with -v (or maybe -v -v). I'd define "reasonable" as "somewhat like how the old fetch worked". Bill State Changed From-To: open->feedback fetch(1) in -CURRENT will now output highly verbose debugging information if the -v option is specified more than once on the command line. State Changed From-To: feedback->closed MFCed, thanks! |