Duplicate repositories: working to convert the darcs repositories
ehuels at gmail.com
Wed Jan 31 08:21:40 UTC 2018
While running the first conversion tests, I ran into the following
repositories (browsable through https://common-lisp.net/cgi-bin/darcsweb.cgi)
already have GitLab repositories in place (<project>/<repository>):
Given the age of all of these repositories, I'm planning to archive these
duplicated repositories and not migrate them to GitLab (as that would mean
the repositories would be either duplicating other repositories or prior
repositories would be overwritten).
Any comments regarding this plan? Maybe someone knows that some of these
repositories need to be migrated to GitLab - replacing what's currently
On Sat, Jan 27, 2018 at 11:56 PM, Erik Huelsmann <ehuels at gmail.com> wrote:
> Hi all,
> After converting common-lisp.net to LetsEncrypt/certbot, I've taken a bit
> of time to research the long-overdue move from darcs to Git.
> Fortunately, taking time away from a task allows for creativity to kick
> in: I've found an (acceptable to me) way to bulk convert all repositories
> listed in https://common-lisp.net/cgi-bin/darcsweb.cgi
> I'm likely to implement a minimal redirect from the existing darcsweb URLs
> to the resulting GitLab git projects. However, since the commit SHAs don't
> match, anything more complex requires pretty extensive mapping tables.
> Please consider this as an invitation to do that work! :-)
> Final announcement of a cut-over will be done 1 week in advance of the
> cut-over itself. Cut-over will roughly take 4 hours when the window is
> there (although I can't imagine anybody actually *using* these repositories
> other than as read-only sources).
> http://efficito.com -- Hosted accounting and ERP.
> Robust and Flexible. No vendor lock-in.
http://efficito.com -- Hosted accounting and ERP.
Robust and Flexible. No vendor lock-in.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the clo-devel