www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Herbert Duerr (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (INFRA-5590) Creating a Git-Mirror of the Openoffice code base
Date Mon, 03 Dec 2012 12:05:58 GMT

     [ https://issues.apache.org/jira/browse/INFRA-5590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Herbert Duerr updated INFRA-5590:
---------------------------------

    Description: 
The OpenOffice project would benefit from having an official git mirror of its codebase. Following
http://www.apache.org/dev/git and the mailing list thread on http://mail-archives.apache.org/mod_mbox/openoffice-dev/201211.mbox/%3C50B88C50.7020506%40apache.org%3E
here are the requested infos:

- 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: There is the standard "trunk, branches, tags" layout, but there also
exist top-level directories such as devtools, ooo-site, pmc, site, symphony, and trunk-orig.
Since these do not really belong to the codebase (as released in source tarballs) these extra
directories can and should be omitted in the git-mirror if they complicate things too much.

Another complication comes from the fact that most branches are one-level deep, but some are
two levels deep (e.g. branches/alg/aw080). Yet another complication comes from the recent
change from incubator/ooo to openoffice/

  was:
The OpenOffice project would benefit from having an official git mirror of its codebase. Following
http://www.apache.org/dev/git and the mailing list thread on http://mail-archives.apache.org/mod_mbox/openoffice-dev/201211.mbox/%3C50B88C50.7020506%40apache.org%3E
here are the requested infos:

- 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 not trivial. There is the standard "trunk, branches, tags" layout,
but also top-level directories such as devtools, ooo-site, pmc, site, symphony, and trunk-orig.
If these complicate things too much then the git-mirror should ignore these extra directories.

Another complication comes from the fact that most branches are one-level deep, but some are
two levels deep (e.g. branches/alg/aw080). Yet another complication comes from the recent
change from incubator/ooo to openoffice/

    
> Creating a Git-Mirror of the Openoffice code base
> -------------------------------------------------
>
>                 Key: INFRA-5590
>                 URL: https://issues.apache.org/jira/browse/INFRA-5590
>             Project: Infrastructure
>          Issue Type: Task
>      Security Level: public(Regular issues) 
>          Components: Git
>            Reporter: Herbert Duerr
>
> The OpenOffice project would benefit from having an official git mirror of its codebase.
Following http://www.apache.org/dev/git and the mailing list thread on http://mail-archives.apache.org/mod_mbox/openoffice-dev/201211.mbox/%3C50B88C50.7020506%40apache.org%3E
here are the requested infos:
> - 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: There is the standard "trunk, branches, tags" layout, but there
also exist top-level directories such as devtools, ooo-site, pmc, site, symphony, and trunk-orig.
Since these do not really belong to the codebase (as released in source tarballs) these extra
directories can and should be omitted in the git-mirror if they complicate things too much.
> Another complication comes from the fact that most branches are one-level deep, but some
are two levels deep (e.g. branches/alg/aw080). Yet another complication comes from the recent
change from incubator/ooo to openoffice/

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message