Opened at 2014-01-08T22:52:17Z
Last modified at 2014-01-09T18:38:53Z
#2148 new defect
--quiet isn't
| Reported by: | joeyh | Owned by: | daira |
|---|---|---|---|
| Priority: | normal | Milestone: | soon |
| Component: | code-frontend-cli | Version: | 1.10.0 |
| Keywords: | usability quiet easy git-annex | Cc: | |
| Launchpad Bug: |
Description
There are several commands where --quiet does not hush extraneous output. The ones I have seen while working on git-annex tahoe support are:
tahoe put outputs a 200 http response message to stderr. I think --quiet should avoid that. But it should not prevent the capability of the file from being output to stdout.
tahoe get $cap $file outputs a message saying it has written $file
Change History (2)
comment:1 Changed at 2014-01-09T18:38:38Z by daira
- Component changed from unknown to code-frontend-cli
- Keywords usability quiet easy added
- Milestone changed from undecided to soon
comment:2 Changed at 2014-01-09T18:38:53Z by daira
- Keywords git-annex added
Note: See
TracTickets for help on using
tickets.
