Accidentally hit Reply instead of Reply-to-all.

---------- Forwarded message ----------
From: Erik Huelsmann <ehuels@gmail.com>
Date: Mon, Mar 9, 2015 at 9:08 PM
Subject: Re: [Clo-devel] Testing GitLab installation & migration nearing completion: steps to cut-over
To: Raymond Toy <toy.raymond@gmail.com>

Hi Raymond,

On Mon, Mar 9, 2015 at 4:41 PM, Raymond Toy <toy.raymond@gmail.com> wrote:

>>>>> "Erik" == Erik Huelsmann <ehuels@gmail.com> writes:

[snip]

Erik> Another important thing to note is that repositories having
Erik> been brought under GitLab control, will no longer be
Erik> available on their old locations. For gitweb, there will be
Erik> redirect rules instated, as will there be for direct
Erik> repository access over https.

Does that mean any repos using hg will get converted too and not be
available from their old locations?

No: they'll stay right where they currently are. I've thought about offering migration to GitLab, but there's relatively little for common-lisp.net to win (I think): we don't support (and won't in the future) repository browsing with any tools (right?). So, all that we'd win is to be able to delete the 'hg' binary from the system. Well, that's too little gain for the pain.

What does this mean for the Trac "Browse Source" button? Will these get updated appropriately?

Hmm. I don't know how to do that, really. Basically, the plan as it's laid out now, assumes that all git projects move their source browsing over to gitlab. CMUCL uses a non-common-lisp.net-standard configuration for Trac. I don't really know how many projects currently do the same. I'll need to look into that. Basically, my solution would be to redirect all "browse", "tickets" and "wiki" urls to the gitlab namespace for those projects that used Trac to go with Git/Darcs.

Not that it matters all that much. I do plan on converting my one and
only hg repo to git, if it's not done for me as part of the migration.

It's planned, but not for this migration. You're absolutely welcome to do it yourself as soon as the system is opened for general access. May I ask that you mark the Mercurial repository in some recognizable way that it should not be migrated, or better yet, that you make a local copy for yourself and remove the repository from the common-lisp.net system, so it doesn't get migrated twice?

Thanks!

Bye,

Erik.

http://efficito.com -- Hosted accounting and ERP.

Robust and Flexible. No vendor lock-in.

Bye,

Erik.

http://efficito.com -- Hosted accounting and ERP.

Robust and Flexible. No vendor lock-in.