Linux maintainer tooling and workflows
 help / color / mirror / Atom feed
From: "Mark Brown" <broonie@kernel.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: tools@linux.kernel.org
Subject: Re: [kernel.org users] b4 auto-thankanator landed in master
Date: Wed, 15 Apr 2020 16:00:00 +0100	[thread overview]
Message-ID: <20200415150000.GE5265@sirena.org.uk> (raw)
In-Reply-To: <20200410210056.wefp3ujj22esoy2r@chatter.i7.local>

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

On Fri, Apr 10, 2020 at 05:00:56PM -0400, Konstantin Ryabitsev wrote:

> Based on your feedback, I added an "auto-thankanator" mode to b4, which 
> will track your use of "b4 am" and "b4 pr" and create convenient 
> templated thank-you replies when you run "b4 ty".

Nice, this solves some problems I've been having with my scripts since
converting to b4!

It seems like this relies on git branch --show-current which isn't
supported by the git in Debian stable, 2.20.1.  The documentation also
says that

   b4 ty -s all

will send everything but it looks like that just lists all the tracked
patches instead (possibly because of the above, I didn't check).  I'm
not sure what it's looking at the current branch for but if it's doing
that it'd be good to be able to tell it to look at a specific branch
instead - 

> Since it's an experimental feature, we just save a .thanks file instead
> of sending it outright -- at least until there's a lot more testing.

It would be good if there was an explicit command for this, it'd be
useful when scripting stuff I think and also when testing things out.

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

  reply	other threads:[~2020-04-15 15:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-10 21:00 b4 auto-thankanator landed in master Konstantin Ryabitsev
2020-04-15 15:00 ` Mark Brown [this message]
2020-04-15 16:57   ` [kernel.org users] " Konstantin Ryabitsev
2020-04-15 17:23     ` Mark Brown
2020-04-15 17:55       ` Konstantin Ryabitsev
2020-04-15 18:32         ` Mark Brown
2020-04-15 19:28           ` Konstantin Ryabitsev
2020-04-15 20:12             ` Mark Brown
2020-04-15 21:21               ` Konstantin Ryabitsev
2020-04-15 21:40                 ` Mark Brown
2020-04-15 22:36                   ` 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=20200415150000.GE5265@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