All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Williams <dan.j.williams@intel.com>
To: tools@linux.kernel.org
Subject: b4 am support for partial series updates?
Date: Fri, 14 May 2021 15:50:21 -0700	[thread overview]
Message-ID: <CAPcyv4ggbuHbqKV33_TpE7pqxvRag34baJrX3yQe-jXOikoATQ@mail.gmail.com> (raw)

I recently had someone grumble at me about my requirement that they
repost a full series just so "b4 am" could autograb the full set even
though only a handful of patches changed.

As an experiment I tried replying to a patch to update and marked it
v5, but b4 am reports:

# b4 am 162096970332.1865304.10280028741091576940.stgit@dwillia2-desk3.amr.corp.intel.com
...
Writing ./v5_20210514_dan_j_williams_cxl_acpi_introduce_acpi0017_driver_and_cxl_root.mbx
  ERROR: missing [1/8]!
  ERROR: missing [2/8]!
  ERROR: missing [3/8]!
  ERROR: missing [4/8]!
  [PATCH v5 5/8] cxl/acpi: Introduce ACPI0017 driver and cxl_root
  ERROR: missing [6/8]!
  ERROR: missing [7/8]!
  ERROR: missing [8/8]!

...which is helpful if v5 was partially sent, but not if all the other
patches don't require updates. This feels like a "WANTVER+" option
that means "grab latest, but fall back to vX" for missing patches. Has
this come up before?

What format would help b4 detect this situation? By default tooling
would make the prefix be [PATCH], I manually made that [PATCH v5 5/8]
and forced the in-reply-to message-id to the v4 version.

I'm nearing the point where handling this manually is more painful
than figuring out a b4 patch, but please consider this for the b4
feature backlog in the meantime.

             reply	other threads:[~2021-05-14 22:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-14 22:50 Dan Williams [this message]
2021-05-16 22:52 ` b4 am support for partial series updates? Konstantin Ryabitsev
2021-05-17 16:13 ` Konstantin Ryabitsev
2021-05-17 17:11   ` Dan Williams

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=CAPcyv4ggbuHbqKV33_TpE7pqxvRag34baJrX3yQe-jXOikoATQ@mail.gmail.com \
    --to=dan.j.williams@intel.com \
    --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.