Re: patch submission process, was Re: [PATCH v6 06/16] merge_recursive: abort properly upon errors
- From
Michael Haggerty <mhagger@alum.mit.edu>
- Date
- Aug 9, 2016, 10:19 UTC
- Message-ID
- <111a9cbe-a174-b8c0-23e5-f7f08635aa6e@alum.mit.edu>
- In-Reply-To
- <CACsJy8DeSv_ALHR+HrViEptgYCYhXu2ZczMmhzZfHGAwZumnzg@mail.gmail.com>
On 08/09/2016 06:22 AM, Duy Nguyen wrote:
Show 13 quoted lines
> On Tue, Aug 9, 2016 at 12:20 AM, Michael Haggerty <mhagger@alum.mit.edu> wrote: >> On 08/04/2016 05:58 PM, Johannes Schindelin wrote: >>> [...] >>> Even requiring every contributor to register with GitHub would be too much >>> of a limitation, I would wager. >>> [...] >> >> Is it *really* so insane to consider moving collaboration on the Git >> project to GitHub or some other similar platform? > > In the very unlikely event that github is shut down, how do we get all > review comments out of it, assuming that we will use pull requests for > review?
I don't have any experience with these tools, but a quick search turns up the following possibilities (among others):
* github-backup (by Joey Hess): https://github.com/joeyh/github-backup * python-github-backup: https://github.com/josegonzalez/python-github-backup * BackHub (commercial service): https://backhub.co/ * Import GitHub project into GitLab: http://docs.gitlab.com/ce/workflow/importing/import_projects_from_github.html
Michael