Note: because of a bug in our SourceForge.net repository we have temporarily moved to a repository on code.inrain.org (hosted by Noya). We'll move back as soon as the SourceForge.net people have fixed that bug.
You can browse the repository online:
http://code.inrain.org/browse/glou/
If you want to be updated when someone commits to the repository, you can subscribe to the commit mailinglist:
http://lists.sourceforge.net/lists/listinfo/glou-commits/
+ libglou
| Glou component libglou
| + main
| | main branch (aka trunk)
| |
| + 0.1
| | 0.1 branch for patches and updates backported to v0.1
| |
| + feature_x
| | branch for developing feature x without interrupting main development
| |
| + ...
|
+ libxoup
|
+ game_community_server
|
+ ...
|
+ private
place for user branches
|
+ noya
| branches of Noya
| |
| + foobar
| | something Noya is working on
| |
| + ...
|
+ ...
Bazaar is really easy to learn. If you are new to Bazaar have a look at its documentation:
PATH is the path of the branch you want to access (see Layout). DEST is the destination for the branch on your local machine.
bzr branch http://code.inrain.org/bzr/glou/PATH DEST
e.g.: bzr branch http://code.inrain.org/bzr/glou/libglou/main libglou
First you'll have to contact Noya and send him your public SSH key.
In the following examples, PATH is the path of the branch you want to access (see Layout).
DEST is the destination for the branch on your local machine.
bzr branch bzr+ssh://code-glou@code.inrain.org/PATH DEST
e.g.: bzr branch bzr+ssh://code-glou@code.inrain.org/libglou/main libglou
Get the latest changes:
bzr pull bzr+ssh://code-glou@code.inrain.org/PATH
e.g.: bzr pull bzr+ssh://code-glou@code.inrain.org/libglou/main
Publish your changes:
bzr commit (as often as you like)
bzr push bzr+ssh://code-glou@code.inrain.org/PATH
e.g.: bzr push bzr+ssh://code-glou@code.inrain.org/libglou/main
Bazaar has a useful feature for sending patches: bzr send.
First commit all changes in your current branch. Then run:
bzr send --mail-to glou-devel@lists.sourceforge.net
Bazaar then will create a diff to the parent branch, fire up your favourite mail client, and attach the diff. Now you should describe what your patch does and send the mail. Voilà, you're done.
There is a known problem if you use Thunderbird as your mail client (the patch won't be attached). To fix it simply add mail_client = thunderbird to your Bazaar configuration (~/.bazaar/bazaar.conf).
Wiki: Developer's_Guide
Wiki: Development/Environment
Page with SourceForge.net Repository
...
Browse the repository.
...
...
First you'll have to setup your SourceForge.net SSH Key.
In the following examples, PATH is the path of the branch you want to access (see [[#Layout|Layout]]) and USER is your SourceForge.net username.
...
...
...
...