Workflows Archive on
 help / color / Atom feed
From: Michael Turquette <>
Cc: Lukas Bulwahn <>,,
	Till Kamppeter <>,
	Aveek Basu <>,
	Stephen Boyd <>
Subject: Re: Explore ideas on workflows improvements with Google Summer of Code mentoring program?
Date: Thu, 16 Jan 2020 11:39:43 -0800
Message-ID: <> (raw)
In-Reply-To: <>

On Wed, Jan 15, 2020 at 3:03 PM Bjorn Helgaas <> wrote:
> On Wed, Jan 15, 2020 at 4:07 PM Michael Turquette
> <> wrote:
> > I added the first entry, "Bidirectionally sync Patchwork patch status
> > with Gmail labels". Stephen Boyd and I use a local solution to
> > coordinate patches in the Linux Clk tree. Our solution requires
> > Patchwork + the Notmuch mail indexer + Gmail/G Suite to work. My
> > proposal is to remove the Notmuch requirements and teach Patchwork to
> > talk directly to Gmail (and vice versa), perhaps via a solution in the
> > cloud, running on a server somewhere, and not dependent on the uptime
> > of my laptop.
> >
> > From my discussions with kernel devs, I believe there is a reasonably
> > sized Venn diagram of people that use both Patchwork for patch
> > tracking as well as Gmail/G Suite for email. Having those two talk
> > might mean that I never have to use the Patchwork web interface again,
> > a big win IMO, and I can just use email.
> That's a really cool idea.  What do you do about the Gmail/plain text
> problem?  I know Gmail *can* sent plain-text email, but you don't have
> much control over the formatting, and I really don't like reviewing
> code in a Gmail draft.  I hate to admit it, but I'm always bouncing
> back and forth between Gmail and mutt.

My solution is to not review patches or send plain-text responses with
the Gmail web interface. I use Mutt and alot as my mailers for patch
review. I use the Gmail web interface for everything else.

Mail fetching and syncing (along with bidirection sync of Notmuch tags
and Gmail Labels) is achieved with the excellent Lieer tool:

Only missing feature in that tool is to do something like fetching
only last 30 days of mail (basic feature for offlineimap and friends)
for the "flying with my laptop to Linux conference" use case. Maybe
another GSoC submission if I'm feeling greedy? ;-)

Best regards,

Michael Turquette
CEO - Los Angeles, CA
BayLibre - At the Heart of Embedded Linux
Schedule a meeting:

  reply index

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-14 18:07 Lukas Bulwahn
2020-01-15 22:07 ` Michael Turquette
2020-01-15 23:03   ` Bjorn Helgaas
2020-01-16 19:39     ` Michael Turquette [this message]
2020-01-17  1:34     ` Stephen Boyd
2020-01-16  0:59   ` Daniel Axtens
2020-01-16 19:35     ` Michael Turquette
2020-01-17  2:19       ` Daniel Axtens
2020-01-17 20:25   ` Lukas Bulwahn
2020-01-17 20:38     ` Michael Turquette
2020-01-18  7:18       ` Lukas Bulwahn
2020-01-21 22:14         ` Michael Turquette
2020-01-22  6:18           ` Lukas Bulwahn
2020-01-22 22:22             ` Michael Turquette

Reply instructions:

You may reply publically 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Workflows Archive on

Archives are clonable:
	git clone --mirror workflows/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 workflows workflows/ \
	public-inbox-index workflows

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone