asking. I wanted to let you all know that we have a
>> Linaro organization on github (ping danilos to get your github account
>> included there). I've created the validation team there and allowed it
>> to push/pull to https://github.com/Linaro/lava-deployment-tool I also
&
(ping danilos to get your github account
> included there). I've created the validation team there and allowed it
> to push/pull to https://github.com/Linaro/lava-deployment-tool I also
> have my own fork.
>
>
LAVA is hosted on launchpad. unless you can convince the whole team
we have a
>> Linaro organization on github (ping danilos to get your github account
>> included there). I've created the validation team there and allowed it
>> to push/pull to https://github.com/Linaro/lava-deployment-tool I also
>> have my own fork.
>
> I'm not
On 8 December 2011 01:22, Ricardo Salveti wrote:
> What I just didn't understand much is the relation with
> git.linaro.org, as now it sees we have 2 official git hosting places
> for projects. I know that technically using github is a lot easier, as
> setting up a git repository at git.linaro.org
b account
> included there). I've created the validation team there and allowed it
> to push/pull to https://github.com/Linaro/lava-deployment-tool I also
> have my own fork.
I'm not much concerned about you moving the code hosting to github, as
we already have quite a few projec
it
to push/pull to https://github.com/Linaro/lava-deployment-tool I also
have my own fork.
I wanted to give you a few reasons why I wanted to use github instead
of bzr (note, we've got a bzr mirror setup on launchpad so you can
always get the code from there)
1) Linaro uses git a lot and no
As part of an effort to streamline deployment of LAVA, and allow for a more
continuous testing and deployment process, the Linaro Validation Team has
been working on a tool to assist with deployment of LAVA components. The
intent is to create something that is suitable for production deployments
a
