From: Mark Brown <broonie@kernel.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: tools@linux.kernel.org
Subject: Re: Feature requests
Date: Mon, 12 Dec 2022 12:22:41 +0000 [thread overview]
Message-ID: <Y5cdEWH8+BzYHaxU@sirena.org.uk> (raw)
In-Reply-To: <20221209210932.rabvalmiry2a3zge@meerkat.local>
[-- Attachment #1: Type: text/plain, Size: 1906 bytes --]
On Fri, Dec 09, 2022 at 04:09:32PM -0500, Konstantin Ryabitsev wrote:
> On Tue, Dec 06, 2022 at 11:52:25PM +0000, Mark Brown wrote:
> > 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
...
> > 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.
> I believe the latest master should have what you need:
> $ b4 prep --show-info
> branch: b4/bupkes-bogus
> cover-subject: [RFC] Another completely bogus series, ignore
> prefixes: RFC
> change-id: 20221205-bupkes-bogus-8f0db5172091
> revision: 6
> cover-strategy: commit
> base-branch: master
> base-commit: bce9332220bd677d83b19d21502776ad555a0e73
> start-commit: 8398c66ced5379a8b84d59ec7f703e9809b17c12
> end-commit: ae4436d441721dd884355b637f02dbc620ad422d
> commit-ae4436d44172: Rename linux into pengux
> commit-c0075ed67f3f: Makefile: Make it a ninja penguin
That does the read side great, thanks - the write side would still be
useful, mainly for the base-branch which can change during the lifetime
of a series (it's common to move between mainline and topic branches in
the upstream repo in both directions).
> > - 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.
> Theoretically, this is already possible via tag.gpgSign = yes. Would that be a
> suitable approach?
Yes, that should work for me for now - I guess there will be some people
who do use unsigned tags who'd want to sign these particular tags.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2022-12-12 12:22 UTC|newest]
Thread overview: 9+ 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 ` Feature requests Mark Brown
2022-12-09 21:09 ` Konstantin Ryabitsev
2022-12-12 12:22 ` Mark Brown [this message]
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=Y5cdEWH8+BzYHaxU@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox