All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: tools@linux.kernel.org
Subject: Feature requests
Date: Tue, 6 Dec 2022 23:52:25 +0000	[thread overview]
Message-ID: <Y4/VuYDJq9aUQiPv@sirena.org.uk> (raw)
In-Reply-To: <20221206221546.ezjxmz2w3tuxbzx5@meerkat.local>

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

Hi Konstantin,

I've had another look at potentially adopting b4 prep/send as a
replacement for the bits of my scripting that it covers.  I did
find a couple of gaps that are causing friction though:

 - Some command line options for extracting the metadata for the
   series would be helpful - the main one I'm looking for is
   series.revision, some of my scripts operate on all the
   branches I've got that have unsent changes which I could do by
   comparing the current version with the last sent version.  An
   equivalent of git config get/set for the series metadata would
   cover all this and more.

 - Being able to get the commit ID of the metadata commit would
   be useful so I can do testing on the actual commits in the
   branch (when using the commit cover strategy).  Alternatively,
   I'd use this to generate a list of commits in the branch so
   that list would also do the job, but getting the ID for the
   metadata commit seems more general.

 - It would be nice if there was an option to sign the tags used
   when tagging sent branches, especially when signing the actual
   sent patches.

Thanks for working on b4, it's really useful.

Thanks,
Mark

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  parent reply	other threads:[~2022-12-06 23:52 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-06 22:07 b4 prep HEAD fails when specifying branch point Mark Brown
2022-12-06 22:15 ` Konstantin Ryabitsev
2022-12-06 22:58   ` Mark Brown
2022-12-07  1:11     ` Konstantin Ryabitsev
2022-12-07 12:42       ` Mark Brown
2022-12-07 22:55         ` Mark Brown
2022-12-06 23:52   ` Mark Brown [this message]
2022-12-09 21:09     ` Feature requests Konstantin Ryabitsev
2022-12-12 12:22       ` Mark Brown
  -- strict thread matches above, loose matches on Subject: below --
2004-09-20 19:19 feature requests martin f krafft
2004-09-20 19:33 ` Mads Martin Joergensen
2004-09-20 19:56 ` martin f krafft
2004-09-20 20:04 ` Mads Martin Joergensen
2004-09-20 20:10 ` martin f krafft
2004-09-20 20:24 ` Mads Martin Joergensen
2004-09-20 20:28 ` Mads Martin Joergensen
2004-09-20 20:38 ` martin f krafft
2004-09-20 20:54 ` Mads Martin Joergensen
2004-09-20 20:59 ` martin f krafft
2004-09-20 21:00 ` Mads Martin Joergensen
2004-09-20 21:04 ` martin f krafft
2004-09-20 21:05 ` Mads Martin Joergensen
2004-09-20 21:15 ` martin f krafft
2004-09-20 21:17 ` Mads Martin Joergensen
2004-09-20 21:21 ` martin f krafft
2004-09-20 21:25 ` Mads Martin Joergensen
2004-09-21 10:42 ` Morten K. Poulsen
2004-09-21 14:22 ` martin f krafft
2004-09-21 14:54 ` Morten K. Poulsen
2004-09-21 14:59 ` martin f krafft

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=Y4/VuYDJq9aUQiPv@sirena.org.uk \
    --to=broonie@kernel.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.