doc:git
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
doc:git [2011/12/07 00:49] – Added wrapper repository example, changed externals example to preformatted frozenfire | doc:git [2020/09/03 01:18] (current) – avenger | ||
---|---|---|---|
Line 16: | Line 16: | ||
- [[https:// | - [[https:// | ||
- [[https:// | - [[https:// | ||
+ | - [[https:// | ||
- [[https:// | - [[https:// | ||
- [[https:// | - [[https:// | ||
Line 28: | Line 29: | ||
== Properties == | == Properties == | ||
+ | |||
+ | **svn: | ||
Modules are achieved using the Subversion property known as svn: | Modules are achieved using the Subversion property known as svn: | ||
Subversion paths to be linked into the project by URL. | Subversion paths to be linked into the project by URL. | ||
Line 34: | Line 37: | ||
doc-base https:// | doc-base https:// | ||
en https:// | en https:// | ||
+ | |||
+ | **svn: | ||
+ | Each xml file in the repository contains a set of keywords which are automatically substituted when | ||
+ | checked out. These allow certain terms to be automatically updated for each commit, rather than | ||
+ | maintained manually. Importantly, | ||
+ | of the English translation their file is based upon. | ||
+ | |||
+ | '' | ||
+ | Id Rev Revision Date LastChangedDate LastChangedRevision Author LastChangedBy HeadURL URL | ||
=== Proposed Git Structure === | === Proposed Git Structure === | ||
Line 39: | Line 51: | ||
are required for the transition to Git from Subversion. First and foremost, Git does not support | are required for the transition to Git from Subversion. First and foremost, Git does not support | ||
partial check-outs of a subsection of the repository. | partial check-outs of a subsection of the repository. | ||
- | Because of this, the project | + | Because of this, the project |
repositories whose function is to define a set of submodules that make up each translation' | repositories whose function is to define a set of submodules that make up each translation' | ||
== Doc-Base == | == Doc-Base == | ||
- | Since the doc-base path of the PHP Documentation project is a global dependency for all builds, it makes up its own major project, which all wrapper repositories will include as a submodule. | + | Since the doc-base path of the PHP Documentation project is a global dependency for all builds, it |
+ | makes up its own major project, which all wrapper repositories will include as a submodule. | ||
== " | == " | ||
Line 50: | Line 63: | ||
'' | '' | ||
git init phpdoc-en | git init phpdoc-en | ||
- | git submodule add phpdoc-en/ | + | git submodule add git:// |
- | git submodule add phpdoc-en/ | + | git submodule add git:// |
+ | |||
+ | == Attributes == | ||
+ | Because Git does not support keywords in the same way that Subversion does, some changes may need to be | ||
+ | made, or it may be necessary to create hackish dependencies in order to | ||
+ | [[https:// | ||
+ | |||
+ | '' | ||
+ | git clone git:// | ||
+ | git init phpdoc-en | ||
+ | cat git-rcs-keywords/ | ||
+ | echo '*.xml filter=rcs-keywords' | ||
+ | cp -R git-rcs-keywords/ |
doc/git.1323218976.txt.gz · Last modified: 2017/09/22 13:28 (external edit)