From: jim.cromie@gmail.com
Date: Tue, 10 Feb 2026 00:33:02 GMT
Subject: Re: --suppress-* options error out, apparently passing to format-patch too.
Message-ID: <CAJfuBxzvkMuV3cNB-GvZRLtZ--sz46eGzSSAE+tHePSL44O4sA@mail.gmail.com>
In-Reply-To: <xmqq7bsl30rv.fsf@gitster.g>

On Mon, Feb 9, 2026 at 5:22 PM Junio C Hamano <gitster@pobox.com> wrote:
>
> jim.cromie@gmail.com writes:
>
> > [jimc@godzilla wk-test]$ git send-email --to=$trybot --no-to
> > --suppress-to --no-cc --dry-run
> > 0001-dyndbg-fix-NULL-ptr-on-i386-due-to-section-alignment.patch
> > fatal: unrecognized argument: --suppress-to
> > format-patch -o /tmp/tXB5tLINzc --suppress-to: command returned error: 128
> > [jimc@godzilla wk-test]$ git send-email --to=$trybot --no-to
> > --suppress-to=all --no-cc --dry-run
> > 0001-dyndbg-fix-NULL-ptr-on-i386-due-to-section-alignment.patch
> > fatal: unrecognized argument: --suppress-to=all
> > format-patch -o /tmp/Y47eIqlSDG --suppress-to=all: command returned error: 128
> >
> > --no-to --no-cc also doesnt work (as Id expect), it still wants to cc
> > to one given in patch-file.
>
> My findings from a quick read of the send-email script:
>
>  * There are --suppress-cc and --suppress-from but there is no
>    --suppress-to option at all.
>

Indeed.  my brain filled that in.
once I dropped it, the cmd succeeded.

>  * There are --no-cc and --no-to but they suppress cc and to
>    addresses from the command line (and probably from the
>    configuration); addresses a specific patch file lists to be sent
>    are not affected.
>

yes, that explains things.

> Documentation updates might be needed.

       --no-to, --no-cc, --no-bcc
           Clear any list of To:, Cc:, Bcc: addresses previously set via config.

I did find "config" somewhat ambiguous. "options" would be clearer.

thank you.