|
Documents Download Building Support Wiki Stuff |
Main /
GitMain.Git HistoryHide minor edits - Show changes to output Added lines 3-4:
Many thanks to Sergei Nikulov for his assistance and persistence in enabling the migration from Subversion to Git. Changed lines 11-12 from:
* On OSX and Windows, the [[https://www.atlassian.com/software/sourcetree | SourceTree ]] to:
* On OSX and Windows, the [[https://www.atlassian.com/software/sourcetree | SourceTree ]] tool provides an excellent GUI for Git repository manipulations Changed lines 15-16 from:
The top level URL for these to:
The top level URL for these repositories are: Changed lines 11-21 from:
-> [@svn checkout svn The top level modules are opal and ptlib -> [@ -> [@ The current development version is always in the trunk. There may be snapshots of development versions though this is rare. to:
There are two separate respositories: ptlib, and opal The top level URL for these repositoryies are: -> git://git.code.sf.net/p/opalvoip/ptlib -> git://git.code.sf.net/p/opalvoip/opal The head of the main trunk revision of these modules (which is also the development revision) can be extracted using the following commands: -> [@git clone git://git.code.sf.net/p/opalvoip/ptlib@] -> [@git clone git://git.code.sf.net/p/opalvoip/opal@] Changed lines 24-26 from:
->[@ ->[@ to:
->[@git clone -b vA_B git://git.code.sf.net/p/opalvoip/ptlib@] ->[@git clone -b vC_D git://git.code.sf.net/p/opalvoip/opal@] Changed lines 29-31 from:
->[@ ->[@ to:
->[@git clone -b v2_2 git://git.code.sf.net/p/opalvoip/ptlib@] ->[@git clone -b v3_2 git://git.code.sf.net/p/opalvoip/opa@] Changed lines 34-42 from:
->[@ ->[@ where vA_B_C is the current version e.g. PTLib version 2.8.3 would be v2_8_3, similarly ->[@ ->[@ The to:
->[@git clone -b vA_B_C git://git.code.sf.net/p/opalvoip/ptlib@] ->[@git clone -b vD_E_F git://git.code.sf.net/p/opalvoip/opal@] where vA_B_C is the current version e.g. PTLib version 2.8.3 would be v2_8_3, similarly vD_E_F for OPAL version 3.8.3 would be v3_8_3. For example: ->[@git clone -b v2_8_3 git://git.code.sf.net/p/opalvoip/ptlib@] ->[@git clone -b v3_8_3 git://git.code.sf.net/p/opalvoip/opal@] The Git master branch has odd version numbers and stable revisions are always in branches with even numbers. The development trunk will also be marked as "alpha" when you get version numbers strings from the libraries. The even numbered stable branch are marked as "beta". Only the formally released tar balls, and their associated "tagged" Git tags/branvhes do not have "alpha" or "beta" associated with them. Added lines 1-44:
Opal uses [[ https://git-scm.com/ | Git ]] for project file version control. The repository is hosted by [[ http://sourceforge.net/projects/opalvoip | SourceForge ]] The repository can be [[https://sourceforge.net/p/opalvoip/_list/git?source=navbar| browsed here ]] Anonymous downloads from the Git repository are possible using a number of popular clients: * The "git" command is provided as part of most Unix distributions. SourceForge provides an [[https://sourceforge.net/p/forge/documentation/Git/ | introduction to the git command ]], or there are many that can be found using Google. * On OSX and Windows, the [[https://www.atlassian.com/software/sourcetree | SourceTree ]] tools provides an excellent GUI for Git repository manipulations The top level URL for the repository is: -> [@svn checkout svn://svn.code.sf.net/p/opalvoip/code@] The top level modules are opal and ptlib. The trunk revision of these modules (which is also the development revision) can be extracted using the following commands: -> [@svn checkout svn://svn.code.sf.net/p/opalvoip/code/ptlib/trunk ptlib@] -> [@svn checkout svn://svn.code.sf.net/p/opalvoip/code/opal/trunk opal@] The current development version is always in the trunk. There may be snapshots of development versions though this is rare. To extract a stable branch of OPAL and PTLib, use the following commands ->[@svn checkout svn://svn.code.sf.net/p/opalvoip/code/ptlib/branches/vA_B ptlib@] ->[@svn checkout svn://svn.code.sf.net/p/opalvoip/code/opal/branches/vC_D opal@] where vA_B is the current version e.g. PTLib version 2.2.x would be v2_2, similarly vC_D for OPAL version 3.2.x would be v3_2. For example: ->[@svn checkout svn://svn.code.sf.net/p/opalvoip/code/ptlib/branches/v2_2 ptlib@] ->[@svn checkout svn://svn.code.sf.net/p/opalvoip/code/opal/branches/v3_2 opal@] To extract a formal stable release of OPAL and PTLib, use the following commands ->[@svn checkout svn://svn.code.sf.net/p/opalvoip/code/ptlib/tags/vA_B_C ptlib@] ->[@svn checkout svn://svn.code.sf.net/p/opalvoip/code/opal/tags/vC_D_E opal@] where vA_B_C is the current version e.g. PTLib version 2.8.3 would be v2_8_3, similarly vC_D_E for OPAL version 3.8.3 would be v3_8_3. For example: ->[@svn checkout svn://svn.code.sf.net/p/opalvoip/code/ptlib/tags/v2_8_3 ptlib@] ->[@svn checkout svn://svn.code.sf.net/p/opalvoip/code/opal/tags/v3_8_3 opal@] The SVN trunk has odd version numbers and stable revisions are always in branches with even numbers. The development trunk will also be marked as "alpha" when you get version numbers strings from the libraries. The even numbered stable branch are marked as "beta". Only the formally released tar balls, and their associated "tagged" SVN versions do not have "alpha" or "beta" associated with them. See the Wiki page on [[VersionNumbering| Version Numbering]] for more information on the versions available. |