Re: Another approach for Livy Website
One pub-sub is configured, every time we commit to a "content" branch, the
website gets updated.
On Wed, Jul 19, 2017 at 8:08 PM, Alex Bozarth <ajboz...@us.ibm.com> wrote:
> Thanks, will there be a straight forward process to it for fu
time
> we commit to a "content" branch, the website gets updated.
>
> From: Luciano Resende <luckbr1...@gmail.com>
> To: dev@livy.incubator.apache.org
> Date: 07/19/2017 08:11 PM
> Subject: Re: Another approach for Livy Website
> ---
Re: Another approach for Livy Website
One pub-sub is configured, every time we commit to a "content" branch, the
website gets updated.
On Wed, Jul 19, 2017 at 8:08 PM, Alex Bozarth <ajboz...@us.ibm.com> wrote:
> Thanks, will there be a straight forward process to it for fu
e ---07/19/2017 06:56:52 PM---After my little mistake, a pushing from
> different local repositry, things are fixed and it should be
>
> From: Luciano Resende <luckbr1...@gmail.com>
> To: dev@livy.incubator.apache.org
> Date: 07/19/2017 06:56 PM
> Subject: Re: Another approach fo
com>
To: dev@livy.incubator.apache.org
Date: 07/19/2017 06:56 PM
Subject: Re: Another approach for Livy Website
After my little mistake, a pushing from different local repositry, things
are fixed and it should be ready now:
https://github.com/apache/incubator-livy-website
Thanks
;sai.sai.s...@gmail.com>
> To: dev@livy.incubator.apache.org
> Date: 07/19/2017 05:17 PM
> Subject: Re: Another approach for Livy Website
> --
>
>
>
> Hi Alex, if think the changes are pretty ready, you can create a PR to
> incubator-liv
g
Date: 07/19/2017 05:17 PM
Subject: Re: Another approach for Livy Website
Hi Alex, if think the changes are pretty ready, you can create a PR to
incubator-livy-website.
Thanks
Jerry
On Mon, Jul 17, 2017 at 6:12 PM, Alex Bozarth <ajboz...@us.ibm.com> wrote:
> I have a personal
ed
States
From: Saisai Shao <sai.sai.s...@gmail.com>
To: dev@livy.incubator.apache.org
Date: 07/14/2017 10:35 AM
Subject: Re: Another approach for Livy Website
I think the way Luciano and you mentioned (using template and put old code
into another branch
From: "Alex Bozarth" <ajboz...@us.ibm.com>
To: dev@livy.incubator.apache.org
Date: 07/13/2017 02:27 PM
Subject: Re: Another approach for Livy Website
The issue with that though is by using the template we plan to not use the
current site code, so importing it to
:20 PM
Subject: Re: Another approach for Livy Website
Maybe we can apply the original changes to the master branch and then do
the changes based on it to just keep the history.
On Thu, Jul 13, 2017 at 2:12 PM, Alex Bozarth <ajboz...@us.ibm.com> wrote:
> I don't have a problem wi
10 matches
Mail list logo
