All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: jim.cromie@gmail.com
Cc: git@vger.kernel.org
Subject: Re: --suppress-* options error out, apparently passing to format-patch too.
Date: Mon, 09 Feb 2026 16:22:44 -0800	[thread overview]
Message-ID: <xmqq7bsl30rv.fsf@gitster.g> (raw)
In-Reply-To: <CAJfuBxwJ_=4mh4gBd3Y98rVRWNZ=xyJAiDxMXb+2TEn6uJM_6g@mail.gmail.com> (jim cromie's message of "Mon, 9 Feb 2026 16:42:52 -0700")

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.

 * 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.

Documentation updates might be needed.

  reply	other threads:[~2026-02-10  0:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-09 23:42 --suppress-* options error out, apparently passing to format-patch too jim.cromie
2026-02-10  0:22 ` Junio C Hamano [this message]
2026-02-10  0:33   ` jim.cromie

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqq7bsl30rv.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=jim.cromie@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.