From: "Jason Gunthorpe" <jgg@ziepe.ca>
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: Mon, 23 Mar 2020 09:16:20 -0300 [thread overview]
Message-ID: <20200323121620.GX20941@ziepe.ca> (raw)
In-Reply-To: <20200320214532.wvmym643l3dw24qh@chatter.i7.local>
On Fri, Mar 20, 2020 at 05:45:32PM -0400, Konstantin Ryabitsev wrote:
> Hi, all:
>
> For my next B4 trick, I plan to add some basic gmail integration --
> since I know many of you do use gmail.
FWIW, I've done some work on this here to avoid the 'OAUTH Apocalypse'
that is coming. You may find the oauth code helpful:
https://github.com/jgunthorpe/cloud_mdir_sync
Getting an oauth application from Google is a bit hard unfortunately.
> 3. Optionally, also send a "thanks, applied" templated reply after you
> do "b4 am"
>
> (#3 will also be available if we find a sendemail.smtpserver.)
If you have a gmail credential then send email can be done over REST
too.
I would second what other people say, my usual work flow is to apply
to get, evaluate and then ack the messages. Today I have a small
script to open the thread covering the patches in git in Mutt so I can
fiddle as I like.
Would enjoy a b4 command to mark git commits as applied in patchworks
based on their Link: header :)
Jason
next prev parent reply other threads:[~2020-03-23 12:16 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
2020-03-23 12:06 ` [tools] " Mark Brown
2020-03-23 12:16 ` Jason Gunthorpe [this message]
2020-03-27 12:53 ` [kernel.org users] " 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=20200323121620.GX20941@ziepe.ca \
--to=jgg@ziepe.ca \
--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).