On Fri, 2015-07-10 at 16:09 -0700, Darren Hart wrote:
> This simple tool should not run on the client IMO. Or should be *required* to
> run on the client. The kernel.org patch submission web form would be usable by
> anyone with a browser ... OK, go ahead... "anyone with a browser" is too low a
> bar for a kernel developer.... :-)
> 
> But seriously, we're talking about recruitment, and this is the kind of tooling
> I routinely here non-Linux developers shake their heads at when considering our
> development process. So while you and I are fine using vi (*jab*) and mutt
> (*evolution) and arcane bash (*posix shell*) scripts and local MTAs... others
> would very much like to focus on the code they are changing, and let the
> computers handle schlepping the changesets around. Especially when they only
> have a couple of patches to send, the setup is significant barrier.

Can you really do kernel development without touching a command line?

Perhaps we need a graphical tool based on gitk in which you can select
a set of commits, edit a cover letter and (initially autogenerated) set
of recipients, and then it'll send them for you?

-- 
dwmw2