OT: mail-based interfaces and web-based interfaces (Re: Extract Git classes from git-svn (1/10))

Michael G Schwern wrote:

And again, it *does not have to be zero sum*.  It doesn't have to be email VS
GUI.  You can have your cake and eat it too.

I assume you're talking about web-based interfaces that have gateways
to email, that produce inboxes like this:

 24 Jul 02:46	GitHub	[github] msysgit/msysgit was forked by peters
 23 Jul 10:27	GitHub	[msysgit/git] ce8ebc: vcs-svn: rename check_o
 23 Jul 10:01	GitHub	[github] Comment created on issue 44 (new git
 23 Jul 09:50	GitHub	[github] Comment created on issue 44 (new git
 23 Jul 09:33	GitHub	[github] Comment created on issue 44 (new git
 23 Jul 09:39	GitHub	[github] Comment created on issue 24 (Long fi
 23 Jul 09:31	GitHub	[github] Comment created on issue 44 (new git
 23 Jul 09:30	GitHub	[github] Comment created on issue 24 (Long fi
 22 Jul 23:57	GitHub	[github] Comment created on issue 44 (new git

I call that pretending to have my cake, rather than having it. :)

Maybe some day someone will prove me wrong and make a nice web-based
tool that I don't even need to know about that mines project mailing
lists.  If I have to tweak my subject lines a little to help it out,
that's fine with me.  I think patchwork is supposed to work this way.

But unless we're talking about splitting the mailing list into a bunch
of mini mailing lists (like some bug trackers do), it doesn't change
anything fundamental, so I'm not sure why we're discussing this.

Ciao,
Jonathan