From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: tools@linux.kernel.org,
"Martin K. Petersen" <martin.petersen@oracle.com>,
users@linux.kernel.org
Subject: Re: [tools] b4 v0.4.0 available with new features
Date: Tue, 28 Apr 2020 23:25:40 -0400 [thread overview]
Message-ID: <yq1ees77z2j.fsf@oracle.com> (raw)
In-Reply-To: <20200428151656.5qz5yiclxmffcnga@chatter.i7.local> (Konstantin Ryabitsev's message of "Tue, 28 Apr 2020 11:16:56 -0400")
Konstantin,
> Interesting -- did you modify the subjects of those commits as well?
> We're already falling back to matching by subject when we can't find
> exact patch-id matches.
I had a couple of cases where I didn't and still got failures. I tried
tweaking the b4 files in .local to match the updated subject to see if I
could convince it to proceed that way but no such luck.
In any case: I do modify subject and commit descriptions for a
substantial amount of the patches I apply. Lots of typos, missing scsi:
tag, wrong driver tag, excessively long lines, etc. I have a hook script
that does a bunch of sanity checking on each patch and won't let me
apply until all issues are addressed.
> b4 ty -s 1,2,3
>
> will always generate a .thanks file for those series, and will omit
> comit-id information when not found.
>
> Does that sound okay?
Sure. If you could still emit the %{summary} boilerplate with XXXXXXXX
as commit hash so it's easy to update afterwards, that would be great.
Thanks!
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2020-04-29 3:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-24 17:04 b4 v0.4.0 available with new features Konstantin Ryabitsev
2020-04-24 23:35 ` [tools] " Martin K. Petersen
2020-04-27 18:40 ` Konstantin Ryabitsev
2020-04-28 2:12 ` Martin K. Petersen
2020-04-28 15:16 ` Konstantin Ryabitsev
2020-04-29 3:25 ` Martin K. Petersen [this message]
2020-04-28 16:03 ` [kernel.org users] " Jason Gunthorpe
2020-05-04 17:09 ` [kernel.org users] " Rob Herring
2020-05-04 17:17 ` Jason Gunthorpe
2020-05-04 20:09 ` Konstantin Ryabitsev
2020-05-04 23:07 ` Jason Gunthorpe
2020-05-04 20:03 ` Konstantin Ryabitsev
2020-05-04 22:58 ` Jason Gunthorpe
2020-05-04 23:04 ` Rob Herring
2020-05-06 19:23 ` Rob Herring
2020-05-07 20:20 ` Konstantin Ryabitsev
2020-05-12 19:07 ` Rob Herring
2020-06-09 22:24 ` Rob Herring
2020-07-27 14:52 ` 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=yq1ees77z2j.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=konstantin@linuxfoundation.org \
--cc=tools@linux.kernel.org \
--cc=users@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 NNTP newsgroup(s).