[cip-dev] Important: planned movement of the cip-kernel repo on Gitlab: Thursday 19th April 10:00 UTC

[cip-dev] Important: planned movement of the cip-kernel repo on Gitlab: Thursday 19th April 10:00 UTC

[Agustín Benito Bethencourt]

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

[cip-dev] Important: planned movement of the cip-kernel repo on Gitlab: Thursday 19th April 10:00 UTC

[Agustín Benito Bethencourt]

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] Important: planned movement of the cip-kernel repo on Gitlab: Thursday 19th April 10:00 UTC

[Zoran S]

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! ;-)

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

[cip-dev] Important: planned movement of the cip-kernel repo on Gitlab: Thursday 19th April 10:00 UTC

[Agustín Benito Bethencourt]

Hi,

On Thursday, 19 April 2018 10:51:28 CEST Agust?n Benito Bethencourt 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

This is no longer the repo location.

> > * The new URL will be: https://gitlab.com/cip-project/cip-kernel/linux-cip

I confirm this is the new URL. Please act accordingly.

> > 
> > 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

Best Regards
-- 
Agust?n Benito Bethencourt
Principal Consultant
Codethink Ltd

[cip-dev] Important: planned movement of the cip-kernel repo on Gitlab: Thursday 19th April 10:00 UTC

[Agustín Benito Bethencourt]

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

[cip-dev] Important: planned movement of the cip-kernel repo on Gitlab: Thursday 19th April 10:00 UTC

[Zoran S]

> We use gitlab based on a TSC (Technical Steering Committee) decision.

TSC should reconsider (at least to duplicate).

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

[cip-dev] Important: planned movement of the cip-kernel repo on Gitlab: Thursday 19th April 10:00 UTC

[Agustín Benito Bethencourt]

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

[cip-dev] Important: planned movement of the cip-kernel repo on Gitlab: Thursday 19th April 10:00 UTC

[Zoran S]

> And the arguments for such reconsideration in your opinion are.... ?

Freedom of choice, for the comfortability and usability reasons.

Zoran
_______

On Mon, Apr 23, 2018 at 6:56 PM, Agust?n Benito Bethencourt
<agustin.benito@codethink.co.uk> wrote:
> 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