tools.linux.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Konstantin Ryabitsev" <konstantin@linuxfoundation.org>
To: tools@linux.kernel.org
Cc: Mark Brown <broonie@kernel.org>
Subject: Re: [tools] b4 ty thanking for everything
Date: Tue, 1 Dec 2020 10:43:54 -0500	[thread overview]
Message-ID: <20201201154354.fw32bk44e6myyi3y@chatter.i7.local> (raw)
In-Reply-To: <164CA10C94033C15.5074@linux.kernel.org>

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

On Tue, Dec 01, 2020 at 10:23:57AM -0500, Konstantin Ryabitsev via linux.kernel.org wrote:
> > as of a git update from master earlier today (I'm at 45c63bd0fd80 
> > "Fix
> > headers generated by "b4 ty") b4 generates thanks for every patch in its
> > database regardless of if it finds any commits for that series in the
> > specified branch which isn't ideal, especially if one has been applying
> > things to multiple branches.
> 
> Dang, this means 0.5.3 is probably broken the same way. Let me find 
> the culprit. :/

Okay, this should be fixed both in master and stable-0.5.y. You can 
restore the damage by looking in your .local/share/b4, finding the .sent 
files that you know were wrongfully triggered, and renaming them back 
into .am.

Sorry about that.

-K

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

  parent reply	other threads:[~2020-12-01 15:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-01 14:41 b4 ty thanking for everything Mark Brown
2020-12-01 14:52 ` [tools] " Martin K. Petersen
2020-12-01 15:23 ` Konstantin Ryabitsev
     [not found] ` <164CA10C94033C15.5074@linux.kernel.org>
2020-12-01 15:43   ` Konstantin Ryabitsev [this message]
2020-12-02 17:05     ` [tools] " Mark Brown

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=20201201154354.fw32bk44e6myyi3y@chatter.i7.local \
    --to=konstantin@linuxfoundation.org \
    --cc=broonie@kernel.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;
as well as URLs for NNTP newsgroup(s).