Linux maintainer tooling and workflows
 help / color / mirror / Atom feed
From: "Erik Schilling" <erik.schilling@linaro.org>
To: "Kernel.org Tools" <tools@linux.kernel.org>
Subject: [BUG b4] To/Cc addresses from cover ignored when sending single patch
Date: Thu, 28 Sep 2023 06:54:21 +0200	[thread overview]
Message-ID: <CVUA1530PTVV.1EL4MWO5N2JNI@ablu-work> (raw)

Hi!

When sending a single-patch, it looks like the To: / Cc: fields from
the "cover" get ignored:

  ❯ git log
  commit caa2c0499a3aa347804c305a8e0394f6736df7a5 (HEAD -> b4/useless-clone)
  Author: Erik Schilling <erik.schilling@linaro.org>
  Date:   Thu Sep 28 06:34:22 2023 +0200

      Some commit
    
      Signed-off-by: Erik Schilling <erik.schilling@linaro.org>

  commit 7850ad017545e8cd16872f07bf774f1549a21624
  Author: Erik Schilling <erik.schilling@linaro.org>
  Date:   Thu Sep 28 06:31:59 2023 +0200

      Some cover
    
      To: Linux-GPIO <linux-gpio@vger.kernel.org>
      Cc: Viresh Kumar <viresh.kumar@linaro.org>
    
      Signed-off-by: Erik Schilling <erik.schilling@linaro.org>
    
      --- b4-submit-tracking ---
      # This section is used internally by b4 prep for tracking purposes.
      {
        "series": {
          "revision": 1,
          "change-id": "20230928-useless-clone-af75c3a58df7",
          "prefixes": [
            "libgpiod"
          ]
        }
      }


  ❯ b4 send -o /tmp/test/
  Converted the branch to 1 messages
  CRITICAL: Could not find any destination addresses (try: b4 prep --auto-to-cc).

See example here: https://github.com/Ablu/libgpiod/tree/b4/useless-clone

Once I add a second commit, everything works.

- Erik

                 reply	other threads:[~2023-09-28  4:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CVUA1530PTVV.1EL4MWO5N2JNI@ablu-work \
    --to=erik.schilling@linaro.org \
    --cc=tools@linux.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).