All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Noralf Trønnes" <noralf@tronnes.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
	tools@linux.kernel.org
Cc: "Noralf Trønnes" <noralf@tronnes.org>
Subject: Re: new: b4 send --reflect
Date: Wed, 7 Dec 2022 17:39:40 +0100	[thread overview]
Message-ID: <f8d14fd5-58e0-853d-64e0-72cc60e69629@tronnes.org> (raw)
In-Reply-To: <20221206215340.556ov3bdfyf3qvyy@meerkat.local>

[-- Attachment #1: Type: text/plain, Size: 1887 bytes --]



Den 06.12.2022 22.53, skrev Konstantin Ryabitsev:
> Hi, all:
> 
> Final feature before 0.11 (hopefully) -- there is a new test mode for b4 send
> that will only email the series to yourself instead of the actual destinations
> listed in "To" or "Cc" headers.
> 
> This should be particularly useful to anyone using the web submission
> endpoint, because this will allow them to see any post-processing that the
> remote will do to their patches (such as rewriting From: for DMARC purposes).
> 

I've always sent the patches to myself for a final check before sending
them off, so this is perfect.

But it doesn't work for me yet:

$ ~/projects/b4/b4.sh send --hide-cover-to-cc --reflect
Converted the branch to 1 messages
---
To: dri-devel@lists.freedesktop.org
    tzimmermann@suse.de
    kernel test robot <lkp@intel.com>
    Noralf Trønnes <noralf@tronnes.org>
---
  [PATCH] drm/gud: Fix missing include
---
Ready to:
  - send the above messages to just noralf@tronnes.org (REFLECT MODE)
  - via web endpoint: https://lkml.kernel.org/_b4_submit

Press Enter to proceed or Ctrl-C to abort
---
Reflecting via web endpoint https://lkml.kernel.org/_b4_submit
Error from endpoint: This service only accepts patches
---
CRITICAL: Was not able to send messages.

$ ~/projects/b4/b4.sh --version
0.11.0-dev-b77ec

Cover letter:

$ git show 6c2812de7efe
commit 6c2812de7efe27951c95c9f736215675009da3fb
Author: Noralf Trønnes <noralf@tronnes.org>
Date:   Wed Dec 7 12:58:01 2022 +0100

    dummy
    Cc: dri-devel@lists.freedesktop.org
    Cc: tzimmermann@suse.de

    --- b4-submit-tracking ---
    # This section is used internally by b4 prep for tracking purposes.
    {
      "series": {
        "revision": 1,
        "change-id": "20221207-gud-missing-include-9ccf56382f8a",
        "base-branch": null
      }
    }

I've attached the 'b4 send --hide-cover-to-cc -o' output.

Noralf.

[-- Attachment #2: b4-gud-missing-include-1.tar.gz --]
[-- Type: application/x-gzip, Size: 1125 bytes --]

  reply	other threads:[~2022-12-07 16:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-06 21:53 new: b4 send --reflect Konstantin Ryabitsev
2022-12-07 16:39 ` Noralf Trønnes [this message]
2022-12-07 18:12   ` Noralf Trønnes
2022-12-07 18:21   ` Konstantin Ryabitsev
2022-12-07 19:36     ` Noralf Trønnes
2022-12-07 19:45       ` Konstantin Ryabitsev
2022-12-07 19:54         ` Noralf Trønnes
2022-12-07 20:07           ` Konstantin Ryabitsev

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=f8d14fd5-58e0-853d-64e0-72cc60e69629@tronnes.org \
    --to=noralf@tronnes.org \
    --cc=konstantin@linuxfoundation.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 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.