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

Re: [PATCH] transport: report missing submodule pushes consistently on stderr

From
Stefan Beller <sbeller@google.com>
Date
Aug 24, 2016, 16:35 UTC
Message-ID
<CAGZ79kb1ur=s+FYcdCh+obKyfaozX=adAPESu9G9FQxVtLTDbg@mail.gmail.com>
In-Reply-To
<20160824122828.0c2688e8@labs-064.localdomain>

On Wed, Aug 24, 2016 at 3:28 AM, Leandro Lucarella <leandro.lucarella@sociomantic.com> wrote:

Show 21 quoted lines
> On Tue, 23 Aug 2016 14:40:08 -0700
> Stefan Beller <sbeller@google.com> wrote:
>> The surrounding advice is printed to stderr, but the list of
>> submodules is not. Make the report consistent by reporting everything
>> to stderr.
>>
>> Signed-off-by: Stefan Beller <sbeller@google.com>
>> ---
>>
>>   This fixes one of the bugs mentioned in
>>   https://public-inbox.org/git/CAGZ79kbkyupBJfvyX3Hj_R5ZW36+3ufOnnLC-Dpic40nPJAxDA@mail.gmail.com/T/#t
>>
>>   How to fix the other was not as obvious to me as I do not
>> understand the philosophy on verbosity in the transport code.
>
> I had a look and I would say just enclose all the fprintf() inside a:
>
>         if (transport->verbose > 0)
>
> But then this is the first time I look at the code. I was about to send
> a patch too but it will conflict with this one :)
Well you can still send a patch :)
We have
    int verbose = (transport->verbose > 0);
    int quiet = (transport->verbose < 0);

So you're suggesting to only print these warnings when the user asked for explicit verbose?

A few lines before the call to die_with_unpushed_submodules we have
     die ("Failed to push all needed submodules!");
which would also need a wrapping like
    if (quiet)
        return -1;
    else
        die(...);

Thanks, Stefan

Previous: Leandro LucarellaNext: Stefan Beller
Message 3 of 4 in “transport: report missing submodule pushes consistently on stderr”
  1. transport: report missing submodule pushes consistently on stderrStefan Beller, Aug 23, 2016
  2. Leandro LucarellaAug 24, 2016
  3. Stefan BellerAug 24, 2016
  4. Stefan BellerAug 26, 2016

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.