You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Herbert Duerr (JIRA)" <ji...@apache.org> on 2012/12/03 11:39:58 UTC
[jira] [Created] (INFRA-5590) Creating a Git-Mirror of the
Openoffice code base
Herbert Duerr created INFRA-5590:
------------------------------------
Summary: 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: 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/
--
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
[jira] [Updated] (INFRA-5590) Creating a Git-Mirror of the
Openoffice code base
Posted by "Herbert Duerr (JIRA)" <ji...@apache.org>.
[ 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/
The sizes of current trunk/main + trunk/ext_libraries are 900MB + 128K, the size of the localization data in trunk/extras is another 860MB. Trunk/ext_sources used to be up to 200MB, but these tarballs can be omitted from the repository. The localization data compresses well but can be considered an own entity, if this makes things easier or m
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: 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/
The sizes of current trunk/main + trunk/ext_libraries are 900MB + 128K, the size of the localization data in trunk/extras is another 860MB. Trunk/ext_sources used to be up to 200MB, but these tarballs can be omitteddisappear from the repository. The localization data can be don't re
> 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/
> The sizes of current trunk/main + trunk/ext_libraries are 900MB + 128K, the size of the localization data in trunk/extras is another 860MB. Trunk/ext_sources used to be up to 200MB, but these tarballs can be omitted from the repository. The localization data compresses well but can be considered an own entity, if this makes things easier or m
--
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
[jira] [Updated] (INFRA-5590) Creating a Git-Mirror of the
Openoffice code base
Posted by "Herbert Duerr (JIRA)" <ji...@apache.org>.
[ 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/
The sizes of current trunk/main + trunk/ext_libraries are 900MB + 128K, the size of the localization data in trunk/extras is another 860MB. Trunk/ext_sources used to be up to 200MB, but these tarballs can be omitteddisappear from the repository. The localization data can be don't re
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: 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/
> 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/
> The sizes of current trunk/main + trunk/ext_libraries are 900MB + 128K, the size of the localization data in trunk/extras is another 860MB. Trunk/ext_sources used to be up to 200MB, but these tarballs can be omitteddisappear from the repository. The localization data can be don't re
--
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
[jira] [Updated] (INFRA-5590) Creating a Git-Mirror of the
Openoffice code base
Posted by "Herbert Duerr (JIRA)" <ji...@apache.org>.
[ 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/
The sizes of current trunk/main + trunk/ext_libraries are 900MB + 128K, the size of the localization data in trunk/extras is another 860MB. The localization data compresses well but can be considered an own entity, if this makes things easier or more manageable (e.g. the old OOo project had separate repositories for the code and the l10 data). The tarballs in trunk/ext_sources used another big chunk of up to 200MB, but they can be omitted altogether, as these external dependencies are fetched after the configure step from their respective original or more reliable backup locations.
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: 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/
The sizes of current trunk/main + trunk/ext_libraries are 900MB + 128K, the size of the localization data in trunk/extras is another 860MB. Trunk/ext_sources used to be up to 200MB, but these tarballs can be omitted from the repository. The localization data compresses well but can be considered an own entity, if this makes things easier or m
> 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/
> The sizes of current trunk/main + trunk/ext_libraries are 900MB + 128K, the size of the localization data in trunk/extras is another 860MB. The localization data compresses well but can be considered an own entity, if this makes things easier or more manageable (e.g. the old OOo project had separate repositories for the code and the l10 data). The tarballs in trunk/ext_sources used another big chunk of up to 200MB, but they can be omitted altogether, as these external dependencies are fetched after the configure step from their respective original or more reliable backup locations.
--
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
[jira] [Updated] (INFRA-5590) Creating a Git-Mirror of the
Openoffice code base
Posted by "Herbert Duerr (JIRA)" <ji...@apache.org>.
[ 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