--quiet isn't #2148

Open
opened 2014-01-08 22:52:17 +00:00 by joeyh · 0 comments
joeyh commented 2014-01-08 22:52:17 +00:00
Owner

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

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
tahoe-lafs added the
unknown
normal
defect
1.10.0
labels 2014-01-08 22:52:17 +00:00
tahoe-lafs added this to the undecided milestone 2014-01-08 22:52:17 +00:00
tahoe-lafs added
code-frontend-cli
and removed
unknown
labels 2014-01-09 18:38:38 +00:00
tahoe-lafs modified the milestone from undecided to soon 2014-01-09 18:38:38 +00:00
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Reference: tahoe-lafs/trac-2024-07-25#2148
No description provided.