documentation:dev:scm:svn
Releases
Current version
Git/Latestdiff: 1.5.6
Latest Snapshots
Produced after each commit or rebase to new upstream version
GIT
RSBAC source code, can be unstable sometimes
Events
No events planned
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
documentation:dev:scm:svn [2006/06/02 15:13] kang underlined michal openssh stuff correctly |
documentation:dev:scm:svn [2006/06/04 09:42] (current) ao Spelling |
||
|---|---|---|---|
| Line 14: | Line 14: | ||
| -- rsbac-1.3 | -- rsbac-1.3 | ||
| -- rsbac-1.3-replication | -- rsbac-1.3-replication | ||
| - | -- rsbac-1.2-virtualusers | + | -- rsbac-1.3-virtualusers |
| * Main 2.4 repository | * Main 2.4 repository | ||
| Line 40: | Line 40: | ||
| </code> | </code> | ||
| - | There are two more repository, ''linux-2.6'' and ''linux-2.4'' which are SVN | + | There are two more repositories, ''linux-2.6'' and ''linux-2.4'' which are SVN |
| copies of the current kernel releases. They are only used for merging. | copies of the current kernel releases. They are only used for merging. | ||
| Line 48: | Line 48: | ||
| * **trunk** is meant to be the latest and greatest, what's currently being worked on. | * **trunk** is meant to be the latest and greatest, what's currently being worked on. | ||
| - | * **tags** contains every releases, they are pulled from trunk or a branch when developpers decides that its stable for a nex release. Bugfixing made for theses very stable releases are based on the ctags versions, not trunk. | + | * **tags** contains every releases, they are pulled from trunk or a branch when developpers decides that its stable for a nex release. Bugfixing made for these very stable releases are based on the ctags versions, not trunk. |
| * **branches** are derivation from the work being done on trunk. They share the same code but are growing their own way. | * **branches** are derivation from the work being done on trunk. They share the same code but are growing their own way. | ||
| Line 71: | Line 71: | ||
| # svn checkout svn://rsbac.org/rsbac-2.6/branches/rsbac-1.2 (or better) | # svn checkout svn://rsbac.org/rsbac-2.6/branches/rsbac-1.2 (or better) | ||
| Everything in this repository: | Everything in this repository: | ||
| - | # svn checkount svn://rsbac.org/rsbac-2.6 | + | # svn checkout svn://rsbac.org/rsbac-2.6 |
| </code> | </code> | ||
| - | //For developpers with write access// | + | //For developers with write access// |
| <code> | <code> | ||
| Development version: | Development version: | ||
| Line 87: | Line 87: | ||
| </code> | </code> | ||
| - | === Great, what about comitting, updating, etc ? === | + | === Great, what about committing, updating, etc ? === |
| The following steps are executed from your checkout directory. | The following steps are executed from your checkout directory. | ||
| Line 109: | Line 109: | ||
| </code> | </code> | ||
| - | A list of the modified file will be presented to you. Check that you modified | + | A list of the modified files will be presented to you. Check that you modified |
| only what you wanted. Do not make a commit for every next file, but for a set | only what you wanted. Do not make a commit for every next file, but for a set | ||
| of changes instead. Make **sure** to write a message about what you did (e.g.: Added feature XXX. Fixed Mantis Bug #3840). If you do not, we will get you and kill you :-) | of changes instead. Make **sure** to write a message about what you did (e.g.: Added feature XXX. Fixed Mantis Bug #3840). If you do not, we will get you and kill you :-) | ||
| Line 198: | Line 198: | ||
| </code> | </code> | ||
| - | From now on, after initiating first connection to rsbac.org with ssh -M username@server you'll get unix socket file inside .ssh which all next connections to the same server will be (re)using. Do not close master connection ! If you have nothing to do on rsbac.org (you don't ;) issue ssh -M -f user@server sleep 10000 - this way ssh will fork into background, keeping your precious master connection in up and running. No svn modification is necesary, ssh takes care about everything itself. | + | From now on, after initiating first connection to rsbac.org with ssh -M username@server you'll get unix socket file inside .ssh which all next connections to the same server will be (re)using. Do not close master connection ! If you have nothing to do on rsbac.org (you don't ;) issue ssh -M -f user@server sleep 10000 - this way ssh will fork into background, keeping your precious master connection in up and running. No svn modification necessary, ssh takes care about everything itself. |
| Now you can try svn commands and see how much faster it is - you __will__ be shocked ! | Now you can try svn commands and see how much faster it is - you __will__ be shocked ! | ||
documentation/dev/scm/svn.1149253997.txt.gz · Last modified: 2006/06/02 15:14 (external edit)