Your message dated Thu, 11 Feb 2010 22:10:04 -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 #447395,
regarding git-pull -t abuses stderr
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.)
--
447395: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=447395
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: git-core
Version: 1:1.5.3.4-1
Severity: normal
* refs/tags/8.69: storing tag '8.69' of
ssh://git.kitenet.net/srv/git/kitenet.net/alien
tag: 190d51e
The above is output to *stderr*. Stderr should only be used for errors.
(Not the only place where git abuses stderr, but definitely the most
annoying for me, since I now have to grep that out by hand from my cronned
git pulls.)
--
see shy jo
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
reopen 529296
notfixed 52926 1:1.6.1.2-1
thanks
Jonathan Nieder wrote:
> 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.
Agh! I closed the wrong bug. Sorry for the trouble.
Mea culpa,
Jonathan
--- End Message ---
