git/list[1] front-page[2] threads[3] people[4] search[5] about
 

git-clone --quiet broken?

From
DJDave Jones <davej@codemonkey.org.uk>
Date
Jul 5, 2008, 21:16 UTC
Message-ID
<20080705211616.GA3874@codemonkey.org.uk>

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: Junio C Hamano
Message 1 of 5 in “git-clone --quiet broken?”
  1. Dave JonesJul 5, 2008
  2. Junio C HamanoJul 6, 2008
  3. Daniel BarkalowJul 6, 2008
  4. Alex RiesenJul 6, 2008
  5. Daniel BarkalowJul 7, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.