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: Mon, 23 Apr 2018 18:56:04 +0200 [thread overview]
Message-ID: <1764316.KvSMvmO5Pl@linux-if6s> (raw)
In-Reply-To: <CAEss1EKhK1b7v99TiDMUnDvNDq7B4tz=i4bYb_HhuiLK+4okeA@mail.gmail.com>
Hi,
On Monday, 23 April 2018 16:00:12 CEST Zoran S wrote:
> > We use gitlab based on a TSC (Technical Steering Committee) decision.
>
> TSC should reconsider (at least to duplicate).
And the arguments for such reconsideration in your opinion are.... ?
>
> Zoran
> _______
>
> On Thu, Apr 19, 2018 at 12:08 PM, Agust?n Benito Bethencourt
>
> <agustin.benito@codethink.co.uk> wrote:
> > Hi Zoran
> >
> > On Thursday, 19 April 2018 12:03:46 CEST Zoran S wrote:
> >> Here, I would like to propose the same to be replicated on GitHub.
> >>
> >> Personally, I do like much more GitHub... But this is me and my
> >> wishes, only! ;-)
> >
> > We use gitlab based on a TSC (Technical Steering Committee) decision.
> >
> >> Zoran
> >>
> >> On Thu, Apr 19, 2018 at 10:51 AM, Agust?n Benito Bethencourt
> >>
> >> <agustin.benito@codethink.co.uk> wrote:
> >> > 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
> >> > _______________________________________________
> >> > cip-dev mailing list
> >> > cip-dev at lists.cip-project.org
> >> > https://lists.cip-project.org/mailman/listinfo/cip-dev
> >
> > --
> > Agust?n Benito Bethencourt
> > Principal Consultant
> > Codethink Ltd
--
Agust?n Benito Bethencourt
Principal Consultant
Codethink Ltd
next prev parent reply other threads:[~2018-04-23 16:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-12 15:37 [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 8:51 ` 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 [this message]
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=1764316.KvSMvmO5Pl@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