FGAddon: Difference between revisions

Jump to navigation Jump to search
6 bytes added ,  29 February 2016
→‎Sending external git repository changes into FGAddon: Switched to {{fgaddon source}} for the SourceForge repository path.
(→‎Individual developer (git-svn): Switched to {{fgaddon source}} and {{repo link}} for the SourceForge repository paths.)
(→‎Sending external git repository changes into FGAddon: Switched to {{fgaddon source}} for the SourceForge repository path.)
Line 839: Line 839:


Firstly clone the FGAddon aircraft into a local git-svn repository with:
Firstly clone the FGAddon aircraft into a local git-svn repository with:
<syntaxhighlight lang="bash">
{{#tag:syntaxhighlight|
git svn clone svn+ssh://<username>@svn.code.sf.net/p/flightgear/fgaddon/trunk/Aircraft/<aircraft>
{{fgaddon source|cmd=git svn clone|protocol=svn+ssh|login=<username>|type=svn|path=Aircraft/<aircraft>|full=1}}
</syntaxhighlight>
| lang = "sh"
}}


This will create a new local git repository linked to FGAddon via git-svn.  If the aircraft is new and not present in FGAddon, see the [[#New_aircraft|instructions for adding a new aircraft to FGAddon]].  Next, set up the remote git repository as a remote, and fetch it:
This will create a new local git repository linked to FGAddon via git-svn.  If the aircraft is new and not present in FGAddon, see the [[#New_aircraft|instructions for adding a new aircraft to FGAddon]].  Next, set up the remote git repository as a remote, and fetch it:

Navigation menu