Am 03/08/2015 04:52 PM, schrieb jan i:
On Sunday, March 8, 2015, Marcus<>  wrote:

Am 03/08/2015 02:08 AM, schrieb

Why not move web development as well as the code development into Git?
+1 any Git.

the staging machine is relying on SVN. So, moving to Git would make
changes on the website impossible - until someone rewrites the code that is
doing the staging and publishing, so that it is (maybe additionally) also
working with Git.

Thats what I heard. It doesn't need to be the full truth but sounds logic
for me. ;-)

I think it was said before, we talk about the code not the website. Due to
CMS we cannot currently move the web site so that will remain untouched in

sure, I know that. But maybe Wolf had missed this. That's the reason why I wrote it again. ;-)


  On Mar 1, 2015, at 6:59 PM, Dennis E. Hamilton<>

I'm going to add my +1 to this proposal.

It occurred to me, when looking into the "old OOo SVN dumps" that Rob
has, that there may be many more downstream users that are on Git and that
our being on Git would facilitate accepting appropriately-offered pull
requests to the AOO repository.  It seems this is a lower-friction way of
sending fixes upstream than going the patch creation and submission route.

- Dennis

-----Original Message-----
From: Jürgen Schmidt []
Sent: Tuesday, February 17, 2015 04:01
Subject: Re: [PROPOSAL] move repo to Git.

[ ... ]

If possible to get a git repo only it make sense. That means we don't
have to move any webpage related stuff into git. Just the pure code is
relevant her.

+1 for a git repo


To unsubscribe, e-mail:
For additional commands, e-mail:

Reply via email to