From mboxrd@z Thu Jan  1 00:00:00 1970
From: agustin.benito@codethink.co.uk (=?ISO-8859-1?Q?Agust=EDn?= Benito Bethencourt)
Date: Thu, 19 Apr 2018 10:51:28 +0200
Subject: [cip-dev] Important: planned movement of the cip-kernel repo on
	Gitlab: Thursday 19th April 10:00 UTC
In-Reply-To: <2728424.ub8oesVq9r@linux-if6s>
References: <2728424.ub8oesVq9r@linux-if6s>
Message-ID: <2715410.MnXGQhdvXK@linux-if6s>
To: cip-dev@lists.cip-project.org
List-Id: cip-dev.lists.cip-project.org

Hi,

On Thursday, 12 April 2018 17:37:41 CEST Agust?n Benito Bethencourt wrote:
> Dear CIP lovers,
> 
> this week Ben H. and I agreed that we need a new repo to store the current
> kernel-configs provided by Members. Since we already have several repos
> related with the kernel, the right thing to do is to create a sub-project
> and store them there, so we decrease entropy.
> 
> The new sub-project for CIP kernel related repositories is: https://
> gitlab.com/cip-project/cip-kernel
> 
> Moving the CIP kernel repo to this new sub-project might affect users that
> are pointing to it. The planned movement date is:
> 
> * Thursday 19th April 2018 at 10:00 UTC.

Reminder: this will take place later today.

> 
> In case you can automate the change, here are the links you need to have in
> consideration:
> * The current repo URL is:  https://gitlab.com/cip-project/linux-cip
> * The new URL will be: https://gitlab.com/cip-project/cip-kernel/linux-cip
> 
> Please plan accordingly.
> 
> I have no previous experience moving such big repos on gitlab.com so expect
> some downtine. In the worst scenario, please remember that you can point to
> Ben H. repo: git://git.kernel.org/pub/scm/linux/kernel/git/bwh/linux-cip.git
> 
> The reasons why we do not copy the repo into a new location and then
> deprecate the old one, instead of going for a hard/hot move, are storage
> limitations and failure rate on Gitlab when mirroring such big repos.
> 
> Best Regards


-- 
Agust?n Benito Bethencourt
Principal Consultant
Codethink Ltd