6,566
edits
FGAddon: Difference between revisions
Jump to navigation
Jump to search
→Connecting an existing git repository to FGAddon: Switched to {{fgaddon source}} for the SourceForge repository path.
(→Sending external git repository changes into FGAddon: Switched to {{fgaddon source}} for the SourceForge repository path.) |
(→Connecting an existing git repository to FGAddon: Switched to {{fgaddon source}} for the SourceForge repository path.) |
||
| Line 877: | Line 877: | ||
If a remote git repository containing a developed aircraft already exists, it is possible to connect it to the remote FGAddon repository using the git-svn tools. The following uses the [[#Dedicated_FGAddon_branch|dedicated FGAddon branch technique]]. Firstly, set up the bridge to FGAddon using git-svn in the per-aircraft repository: | If a remote git repository containing a developed aircraft already exists, it is possible to connect it to the remote FGAddon repository using the git-svn tools. The following uses the [[#Dedicated_FGAddon_branch|dedicated FGAddon branch technique]]. Firstly, set up the bridge to FGAddon using git-svn in the per-aircraft repository: | ||
{{#tag:syntaxhighlight| | |||
git svn init svn+ssh | {{fgaddon source|cmd=git svn init|protocol=svn+ssh|login=<username>|type=svn|path=Aircraft/<aircraft>|full=1}} | ||
| lang = "sh" | |||
}} | |||
Where <code><aircraft></code> is the aircraft directory name in FGAddon. Note that this step can be performed without commit access to FGAddon by using a read-only SVN URL instead, but then changes cannot be pushed back to FGAddon ([[#Synchronising|dcommitting]], as it is known in the git-svn terminology). However, this allows upstream FGAddon changes to be integrated into the remote git repository, thus making it easy to prepare changes for submission for FGAddon inclusion using patches sent to the mailing list or sent via other channels. | Where <code><aircraft></code> is the aircraft directory name in FGAddon. Note that this step can be performed without commit access to FGAddon by using a read-only SVN URL instead, but then changes cannot be pushed back to FGAddon ([[#Synchronising|dcommitting]], as it is known in the git-svn terminology). However, this allows upstream FGAddon changes to be integrated into the remote git repository, thus making it easy to prepare changes for submission for FGAddon inclusion using patches sent to the mailing list or sent via other channels. | ||