Christian Perrier wrote:
> I concur to Lars suggestion. Now that D-I switch to a multiple git
> repo, I get something like this when running my cronned "mr -p -q
> update":
> 
> cperrier@mykerinos:~/src/debian/debian-installer/trunk$ mr -q -p update
> U    manual/cs/appendix/preseed.xml
> U    packages/po/sublevel1/ru.po
> Actualisé à la révision 66294.
> Already up-to-date.
> Already up-to-date.
> Already up-to-date.
> Already up-to-date.
> .../...
> 
> In this case, of course, I expect the first lines to display....but th
> emain problem are the "Already up-to-date" lines (which can be removed
> with "git pull -q").

FWIW, my approach to dealing with this is to use chronic from moreutils.
"chronic mr update" nicely supresses all output, while showing all
output when there is an error -- which is handy since it makes it easy
to see the error in the context of the normal output. Also, it can be
applied to any noisy command. :)

Fixing this in mr would require adding non-noisy versions of the
definitions for git_update, svn_update, bzr_update, etc. But then what
if you wanted a quiet commit or some other operation? I'd have to end
up by dubling the number of command definitions in mr. And anyone adding
a new subcommand to their mr configuration would too.

So, I'm inclined to just promote the use of chronic, and leave mr -q
as a way to omit mr's own output, while leaving the output of the
commands it runs unaffected.

-- 
see shy jo

Attachment: signature.asc
Description: Digital signature

Reply via email to