Re: patch submission process, was Re: [PATCH v6 06/16] merge_recursive: abort properly upon errors

On Tue, Aug 09, 2016 at 06:57:05AM -0400, Jeff King wrote:

On Tue, Aug 09, 2016 at 10:11:30AM +0200, Michael J Gruber wrote:

quoted

Maybe two more points of input for the discussion:

off-line capabilities
=====================

The current workflow here seems to work best when you are subscribed to
the git-ml and have your own (local, maybe selective) copy of git-ml in
your (text-based) MUA (mutt, (al)pine, emacs, ...) that can jump right
into git-am and such directly. I'm not sure how important the "off-line"
aspect of that is for some of us, and how that could be replicated on
GitHub - while PRs and such may be Git based behind the scenes there
seems to be no way to clone that info and work from a local clone.
(Don't know if GitLab is more open.)

You can pull it all out via GitHub's HTTP API, but the question is what
format you would use to store it locally (and which tools you would then
use to play with it).

I haven't really tried this lately, though, so I don't know if there is
information that the API would be missing.

I do have a dream of writing a tool that sucks in GitHub PRs to a fake
email thread, lets me make my responses inline in an editor, and then
pushes it back up as PR comments (finding the right positions based on
the quoted context).

You might try https://github.com/joeyh/github-backup