Your message dated Thu, 11 Feb 2010 19:42:28 -0600
with message-id <[email protected]>
and subject line Re: Bug#529296: mr: a --really-quiet option would be handy
has caused the Debian Bug report #529296,
regarding mr: a --really-quiet option would be handy
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
529296: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=529296
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mr
Version: 0.39
Severity: wishlist
I use mr to keep a number of branches on my laptop up to date, so that I
can easily take my laptop and go hack, without having to remember to
copy everything manually onto it.
I run mr from cron. This works fine, since all branches I am mirroring
are publically available. I get an e-mail from cron every few hours,
which contains the output of mr. I have to scan this manually to see if
(and what) went wrong. Using the -q option does not significantly reduce
the amount of text I need to scan.
It would be really handy for me to have a --really-quiet option (by
whatever name), which would suppress all output, unless something went
wrong. Possibly just outputting a single line saying all went OK (and N
branches were updated). This way, I could spend a few less brain cycles
on dealing with this output.
Actually, now that I think of it, it might be possible to generalize
this: a command called something like
suppress-output-unless-there-was-an-error that would capture stdout and
stderr and print nothing if the command exited with 0, else print
everything.
Joey, would you prefer mr --really-quiet or a command to submit to
moreutils? I'd be happy to submit a patch for either.
--- End Message ---
--- Begin Message ---
Version: 1:1.6.1.2-1
Joey Hess wrote:
> # This hack is here because git pull stupidly outputs tag info to stderr.
> # Shut it up but let real errors through, for use in cron.
> quietupdate = mr -s -n update 3>&1 1>/dev/null 2>&3 | egrep -v '(storing
> tag|tag: )' || true
>
> Git seemed, to me, to be the main offender for unnecessary logging to
> stderr. So I filed a bug on it (#447395). The new git --quiet does seem
> to nicely suppress all output in at least usual cases.
Thanks for the update. Please file new bugs if you notice any git being
rude in this way in the future.
--- End Message ---
