You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openoffice.apache.org by Herbert Duerr <hd...@apache.org> on 2012/11/30 11:37:04 UTC

An official Git-Mirror? (was: Our SVN moved from "incubator/ooo" to "openoffice")

On 30.11.2012 09:58, Andre Fischer wrote:
> It would be even more important to have a detailed description of
> setting up a new local git repository.  I understand that that has
> become more complicated as well, if you want to access the "old"
> history.  I really don't want to go back to use svn directly.

It would all be much simpler if we had an official git-mirror [1] of our 
svn-repository. Before filing an issue for this I'd like to get 
consensus on that, even if only lazy consensus.

[1] http://www.apache.org/dev/git

For the requested infos I suggest:
- Name of the codebase: "Apache OpenOffice"
- Name of the requested Git mirror: "openoffice.git"
- Subversion path of the codebase: "openoffice" (was "incubator/ooo")
- Subversion layout: this is a tricky one, as we have the standard 
"trunk, branches, tags", but also top-level directories such as 
devtools, ooo-site, pmc, site, symphony, and trunk-orig. I'm inclined to 
ignore these extra directories for our git mirror.

Herbert

Re: An official Git-Mirror?

Posted by Andre Fischer <aw...@gmail.com>.
On 30.11.2012 11:37, Herbert Duerr wrote:
> On 30.11.2012 09:58, Andre Fischer wrote:
>> It would be even more important to have a detailed description of
>> setting up a new local git repository.  I understand that that has
>> become more complicated as well, if you want to access the "old"
>> history.  I really don't want to go back to use svn directly.
>
> It would all be much simpler if we had an official git-mirror [1] of 
> our svn-repository. Before filing an issue for this I'd like to get 
> consensus on that, even if only lazy consensus.
>
> [1] http://www.apache.org/dev/git
>
> For the requested infos I suggest:
> - Name of the codebase: "Apache OpenOffice"
> - Name of the requested Git mirror: "openoffice.git"
> - Subversion path of the codebase: "openoffice" (was "incubator/ooo")
> - Subversion layout: this is a tricky one, as we have the standard 
> "trunk, branches, tags", but also top-level directories such as 
> devtools, ooo-site, pmc, site, symphony, and trunk-orig. I'm inclined 
> to ignore these extra directories for our git mirror.
>

+1

This would make my life so much better.

-Andre

> Herbert

Re: An official Git-Mirror?

Posted by Herbert Duerr <hd...@apache.org>.
On 02.12.2012 11:17, Andrea Pescetti wrote:
> On 30/11/2012 Herbert Duerr wrote:
>> It would all be much simpler if we had an official git-mirror [1] of our
>> svn-repository.
>
> OK, this will also make contributing easier for the new developers who
> know only git, since they will be able to checkout (clone) only trunk,
> branches and tags and submit patches with git format-patch. So they
> won't need to learn (or endure, depending on the individual
> inclinations) SVN to help.

One problem could be that we are not using a standard layout, not only 
because of the extra directories such as ooo-site, trunk-orig, etc. but 
also because we have both one- and two-deep directory levels in 
branches/ such as branches/AOO34/ and branches/alg/aw080/. Eventually 
these have to be consolidated to e.g. alg_aw080.

The status of the Git-Mirroring request can be followed at
   https://issues.apache.org/jira/browse/INFRA-5590

Herbert

Re: An official Git-Mirror?

Posted by Andrea Pescetti <pe...@apache.org>.
On 30/11/2012 Herbert Duerr wrote:
> It would all be much simpler if we had an official git-mirror [1] of our
> svn-repository.

OK, this will also make contributing easier for the new developers who 
know only git, since they will be able to checkout (clone) only trunk, 
branches and tags and submit patches with git format-patch. So they 
won't need to learn (or endure, depending on the individual 
inclinations) SVN to help.

Regards,
   Andrea.