You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@vxquery.apache.org by Eldon Carman <ec...@ucr.edu> on 2015/05/04 05:58:08 UTC

Using git for the site repo

>From monitoring a different apache project, it sounds like we could use git
to manage our website. Is this something we should look into? It would be
nice to standardize on git for our project.

What do you think?

Re: Using git for the site repo

Posted by Steven Jacobs <sj...@ucr.edu>.
I just had a clarifying discussion with Preston, and I withdraw my comment
:)
+1 to his suggestion
Steven

On Sun, May 3, 2015 at 11:09 PM, Till Westmann <ti...@apache.org> wrote:

> Hi Steven,
>
> I understood Preston's proposal to mean that we use git instead of svn,
> but keep everything else the same. I can see how that simplifies our tool
> chain (and I like the idea :) ), but not how it would improve the process.
> Could you elaborate a bit more?
>
> Thanks,
> Till
>
> > On May 3, 2015, at 21:32, Steven Jacobs <sj...@ucr.edu> wrote:
> >
> > I think it would make things more convenient. Based on Asterix
> experience,
> > would it be part of the same git project? The doc update process over
> there
> > still seems a little complicated to me. I was wondering if having it as
> > part of a separate git project might be better.
> > Steven
> >
> >> On Sunday, May 3, 2015, Eldon Carman <ec...@ucr.edu> wrote:
> >>
> >> From monitoring a different apache project, it sounds like we could use
> git
> >> to manage our website. Is this something we should look into? It would
> be
> >> nice to standardize on git for our project.
> >>
> >> What do you think?
> >>
>

Re: Using git for the site repo

Posted by Till Westmann <ti...@apache.org>.
Hi Steven,

I understood Preston's proposal to mean that we use git instead of svn, but keep everything else the same. I can see how that simplifies our tool chain (and I like the idea :) ), but not how it would improve the process. 
Could you elaborate a bit more?

Thanks,
Till

> On May 3, 2015, at 21:32, Steven Jacobs <sj...@ucr.edu> wrote:
> 
> I think it would make things more convenient. Based on Asterix experience,
> would it be part of the same git project? The doc update process over there
> still seems a little complicated to me. I was wondering if having it as
> part of a separate git project might be better.
> Steven
> 
>> On Sunday, May 3, 2015, Eldon Carman <ec...@ucr.edu> wrote:
>> 
>> From monitoring a different apache project, it sounds like we could use git
>> to manage our website. Is this something we should look into? It would be
>> nice to standardize on git for our project.
>> 
>> What do you think?
>> 

Re: Using git for the site repo

Posted by Steven Jacobs <sj...@ucr.edu>.
I think it would make things more convenient. Based on Asterix experience,
would it be part of the same git project? The doc update process over there
still seems a little complicated to me. I was wondering if having it as
part of a separate git project might be better.
Steven

On Sunday, May 3, 2015, Eldon Carman <ec...@ucr.edu> wrote:

> From monitoring a different apache project, it sounds like we could use git
> to manage our website. Is this something we should look into? It would be
> nice to standardize on git for our project.
>
> What do you think?
>