Re: [PATCH 1/3] t6501: use --quiet when testing gc stderr

2018-10-18 Thread Junio C Hamano
Derrick Stolee writes: > This code from builtin/gc.c makes it look like we are doing that: > >     if (gc_write_commit_graph) >     write_commit_graph_reachable(get_object_directory(), 0, > !quiet && !daemonized); > > But really,

Re: [PATCH 1/3] t6501: use --quiet when testing gc stderr

2018-10-18 Thread Derrick Stolee
On 10/18/2018 1:23 AM, Junio C Hamano wrote: "Derrick Stolee via GitGitGadget" writes: From: Derrick Stolee The test script t6501-freshen-objects.sh has some tests that care if 'git gc' has any output to stderr. This is intended to say that no warnings occurred related to broken links.

Re: [PATCH 1/3] t6501: use --quiet when testing gc stderr

2018-10-17 Thread Junio C Hamano
"Derrick Stolee via GitGitGadget" writes: > From: Derrick Stolee > > The test script t6501-freshen-objects.sh has some tests that care > if 'git gc' has any output to stderr. This is intended to say that > no warnings occurred related to broken links. However, when we > have operations that

[PATCH 1/3] t6501: use --quiet when testing gc stderr

2018-10-17 Thread Derrick Stolee via GitGitGadget
From: Derrick Stolee The test script t6501-freshen-objects.sh has some tests that care if 'git gc' has any output to stderr. This is intended to say that no warnings occurred related to broken links. However, when we have operations that output progress (like writing the commit-graph) this