From: "Johannes Berg" <johannes@sipsolutions.net>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: users@linux.kernel.org, tools@linux.kernel.org
Subject: Re: [kernel.org users] B4 and gmail integration features
Date: Fri, 20 Mar 2020 23:03:49 +0100 [thread overview]
Message-ID: <40b68e30fa106d65d0e8451d057ec338a3e002ab.camel@sipsolutions.net> (raw)
In-Reply-To: <20200320220138.axvbfnlmzaajvkwh@chatter.i7.local> (sfid-20200320_230146_618107_4EAB0D91)
On Fri, 2020-03-20 at 18:01 -0400, Konstantin Ryabitsev wrote:
> On Fri, Mar 20, 2020 at 10:49:13PM +0100, Johannes Berg wrote:
> > On Fri, 2020-03-20 at 17:45 -0400, Konstantin Ryabitsev wrote:
> > > 3. Optionally, also send a "thanks, applied" templated reply after you
> > > do "b4 am"
> >
> > I've always thought that somehow this ought to be delayed somehow, since
> > I may apply a patch just to look at it, or to run tests, etc. and then
> > really only make up my mind when I push it out ...
>
> How about we just "remember to thank" and have a separate command "b4
> thank" which will interactively verify patch/series before actually
> sending out the "thanks, applied"?
I think that'd be useful, at least as an option.
Even better if you could run a script there to thank, so that could e.g.
also close patchwork patches at that stage? Once we get patchwork with
msgids :)
johannes
next prev parent reply other threads:[~2020-03-20 22:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-20 21:45 B4 and gmail integration features Konstantin Ryabitsev
2020-03-20 21:49 ` [kernel.org users] " Johannes Berg
2020-03-20 22:01 ` Konstantin Ryabitsev
2020-03-20 22:03 ` Jens Axboe
2020-03-20 22:03 ` Johannes Berg [this message]
2020-03-23 12:06 ` [tools] " Mark Brown
2020-03-23 12:16 ` [kernel.org users] " Jason Gunthorpe
2020-03-27 12:53 ` Ludovic Desroches
2020-03-27 13:14 ` Jason Gunthorpe
2020-03-27 13:34 ` Ludovic Desroches
2020-03-27 13:46 ` Jason Gunthorpe
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=40b68e30fa106d65d0e8451d057ec338a3e002ab.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--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).