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

Re: [PATCH] Implement git clone -v

From
Shawn O. Pearce <spearce@spearce.org>
Date
Oct 8, 2008, 06:02 UTC
Message-ID
<20081008060257.GA15240@spearce.org>
In-Reply-To
<20081007193956.GB536@genesis.frugalware.org>
Miklos Vajna <vmiklos@frugalware.org> wrote:
Show 7 quoted lines
> On Tue, Oct 07, 2008 at 08:21:28AM +0200, Alex Riesen <raa.lkml@gmail.com> wrote:
> > Yes. Does it work? :)
> 
> Yes, it does. I'm not sure how to test it from the testsuite, maybe
> redirect the output to a file and grep in it? It's ugly, that's why I
> did not do so, but if you think a testcase is a musthave for this
> feature then that's the way to go, I guess.

Actually its not a bad way to test the feature. Normally we disable progress if stdout is not a tty. If you redirect to a file then -v should be needed to get anything at all on stderr.

You may be able to just test the size of the file:
	git fetch -v ... >out 2>err &&
	test -s err
-- 
Shawn.
Previous: Miklos VajnaNext: Alex Riesen
Message 6 of 11 in “Forcing progerss output for clone”
  1. Constantine PlotnikovOct 3, 2008
  2. Alex RiesenOct 4, 2008
  3. Implement git clone -vMiklos Vajna, Oct 6, 2008
  4. Alex RiesenOct 7, 2008
  5. Miklos VajnaOct 7, 2008
  6. Shawn O. PearceOct 8, 2008
  7. Alex RiesenOct 8, 2008
  8. Implement git clone -vMiklos Vajna, Oct 8, 2008
  9. Junio C HamanoOct 9, 2008
  10. Shawn O. PearceOct 9, 2008
  11. Miklos VajnaOct 9, 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.