6,566
edits
FGAddon: Difference between revisions
Jump to navigation
Jump to search
→Aircraft development: Added a section about an individual developer developing with SVN.
m (→Commit Access) |
(→Aircraft development: Added a section about an individual developer developing with SVN.) |
||
| Line 262: | Line 262: | ||
The development team will then have commit access to the private repository. | The development team will then have commit access to the private repository. | ||
=== Individual developer === | |||
{{Note|Development scenario: You are an individual developer with FGAddon commit access and will use the native Subversion tools.}} | |||
If you are using the command line Subversion client, you can checkout an individual aircraft with: | |||
<syntaxhighlight lang="bash"> | |||
svn co svn+ssh://<username>@svn.code.sf.net/p/flightgear/fgaddon/trunk/Aircraft/wrightFlyer1903 | |||
</syntaxhighlight> | |||
Where <username> is your SourceForge user name. Alternatively you can checkout all aircraft with: | |||
<syntaxhighlight lang="bash"> | |||
svn co svn+ssh://<username>@svn.code.sf.net/p/flightgear/fgaddon/trunk flightgear-fgaddon | |||
</syntaxhighlight> | |||
Once you have made you changes, commit these to the repository with | |||
<syntaxhighlight lang="bash"> | |||
svn ci | |||
</syntaxhighlight> | |||
You will need to write a detailed commit log message. When committing, it is best to make small modular commits so that each commit corresponds to a single purpose. | |||
=== Using git with FGAddon (by Hooray) <!-- appears to be Hooray from history --> === | === Using git with FGAddon (by Hooray) <!-- appears to be Hooray from history --> === | ||