From: Dave Jones <davej@codemonkey.org.uk>
To: git@vger.kernel.org
Subject: git-clone --quiet broken?
Date: Sat, 5 Jul 2008 17:16:16 -0400 [thread overview]
Message-ID: <20080705211616.GA3874@codemonkey.org.uk> (raw)
The server I run various git snapshots on recently got upgraded to git 1.5.6,
and I started getting a lot more mail from cron than usual.
It seems that passing -q to git-clone at some point changed from 'silent'
to 'slightly less noisy'. Only the difference is so slight that it may
as well be nil..
Here's a normal clone..
Initialize git/.git
Initialized empty Git repository in /home/davej/git-trees/git/.git/
remote: Counting objects: 76925, done.
remote: Compressing objects: 100% (25373/25373), done.
remote: Total 76925 (delta 55699), reused 70336 (delta 50160)
Receiving objects: 100% (76925/76925), 17.09 MiB | 1111 KiB/s, done.
Resolving deltas: 100% (55699/55699), done.
And here's the 'quiet' clone..
Initialize git/.git
remote: Counting objects: 76925, done.
remote: Compressing objects: 100% (25373/25373), done.
remote: Total 76925 (delta 55699), reused 70336 (delta 50160)
Receiving objects: 100% (76925/76925), 17.09 MiB | 1128 KiB/s, done.
Resolving deltas: 100% (55699/55699), done.
Spot the difference :)
It looks even worse in mail from cron, where you get one line of text
for every % that git progresses through.
I could run the clone with 2>/dev/null, but I'd really like to get
mail when something breaks instead of it being totally silent.
I'm assuming this was an unintentional side-effect of some other recent change?
Dave
--
http://www.codemonkey.org.uk
next reply other threads:[~2008-07-05 21:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-05 21:16 Dave Jones [this message]
2008-07-06 0:56 ` git-clone --quiet broken? Junio C Hamano
2008-07-06 1:22 ` Daniel Barkalow
2008-07-06 22:56 ` Alex Riesen
2008-07-07 1:40 ` Daniel Barkalow
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080705211616.GA3874@codemonkey.org.uk \
--to=davej@codemonkey.org.uk \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox