From: agustin.benito@codethink.co.uk (Agustín Benito Bethencourt)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] Important: planned movement of the cip-kernel repo on Gitlab: Thursday 19th April 10:00 UTC
Date: Thu, 12 Apr 2018 17:37:41 +0200 [thread overview]
Message-ID: <2728424.ub8oesVq9r@linux-if6s> (raw)
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.
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
next reply other threads:[~2018-04-12 15:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-12 15:37 Agustín Benito Bethencourt [this message]
2018-04-19 8:51 ` [cip-dev] Important: planned movement of the cip-kernel repo on Gitlab: Thursday 19th April 10:00 UTC Agustín Benito Bethencourt
2018-04-19 10:03 ` Zoran S
2018-04-19 10:08 ` Agustín Benito Bethencourt
2018-04-23 14:00 ` Zoran S
2018-04-23 16:56 ` Agustín Benito Bethencourt
2018-04-24 2:18 ` Zoran S
2018-04-19 10:06 ` Agustín Benito Bethencourt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2728424.ub8oesVq9r@linux-if6s \
--to=agustin.benito@codethink.co.uk \
--cc=cip-dev@lists.cip-project.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox