All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Konstantin Ryabitsev" <konstantin@linuxfoundation.org>
To: Mark Brown <broonie@kernel.org>
Cc: tools@linux.kernel.org
Subject: Re: [kernel.org users] b4 auto-thankanator landed in master
Date: Wed, 15 Apr 2020 17:21:02 -0400	[thread overview]
Message-ID: <20200415212102.22zfvequfcvprgbj@chatter.i7.local> (raw)
In-Reply-To: <20200415201222.GM5265@sirena.org.uk>

On Wed, Apr 15, 2020 at 09:12:22PM +0100, Mark Brown wrote:
> > Yes, we always expect there to be a N,N in that output, which isn't 
> > true in a number of scenarios (like a commit that creates a new file 
> > with only one line).
> 
> > The latest master should properly deal with this situation (as well as 
> > when a patch deletes all lines from a file).
> 
> Did you forget to push...

Haha, classic. Yes, it should be there now.

> I also noticed a couple of other issues.
> 
> One is that if I try to specify a remote branch with 'b4 ty -s all -b
> remote/foo' or whatever b4 doesn't think the branch exists.  I'm doing
> this because I want to be sure I only send out thank you mails for
> things that actually got pushed successfully (in the past I've found
> people get confused if the thanks arrives and they can't see the
> published commit).  It needs a --remote on the git branch command line.

Right, we're only paying attention to local branches right now. I'll 
poke to see what needs to happen to work for remotes.

> The other is that if I don't apply all of a series then b4 ty will
> refuse to generate anything with no way I can see to override. 

I think the master has a change for that as well -- try that out.

> This
> happens a fair amount when people do things like send a new driver along
> with a DT update.  Perhaps an option to allow partial lists (though I
> think that might need more complex templating), or one to generate
> per-patch thanks messages?

I think we can do --partial. Let me ponder how that can be done best.

Thanks,
-K



  reply	other threads:[~2020-04-15 21:21 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 ` [kernel.org users] " Mark Brown
2020-04-15 16:57   ` 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 [this message]
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=20200415212102.22zfvequfcvprgbj@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 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.