FGAddon: Difference between revisions

Jump to navigation Jump to search
36 bytes added ,  29 February 2016
→‎Individual developer (git-svn): Switched to {{fgaddon source}} and {{repo link}} for the SourceForge repository paths.
m (→‎Individual developer: Missing tag.)
(→‎Individual developer (git-svn): Switched to {{fgaddon source}} and {{repo link}} for the SourceForge repository paths.)
Line 806: Line 806:


This is more complicated than using the native SVN tools, but can be useful without having FGAddon commit access, as multiple local commits can be made to be sent to the original aircraft authors or to the development mailing list/forum.  To clone the aircraft of choice into a new git repository, type:
This is more complicated than using the native SVN tools, but can be useful without having FGAddon commit access, as multiple local commits can be made to be sent to the original aircraft authors or to the development mailing list/forum.  To clone the aircraft of choice into a new git repository, type:
<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"
}}


Where <code><username></code> is your SourceForge user name and <code><aircraft></code> is the directory name in the FGAddon repository.  If you do not have commit access, instead type:
Where <code><username></code> is your infrastructure user name and <code><aircraft></code> is the directory name in the FGAddon repository.  If you do not have commit access, instead type:
<syntaxhighlight lang="bash">
{{#tag:syntaxhighlight|
git svn clone https://svn.code.sf.net/p/flightgear/fgaddon/trunk/Aircraft/<aircraft>
{{fgaddon source|cmd=git svn clone|type=svn|path=Aircraft/<aircraft>|full=1}}
</syntaxhighlight>
| lang = "sh"
}}


To use the new local git repository, see the [[#Git-svn|git-svn instructions]] and [[#Deficiencies_of_git-svn|its deficiencies]].
To use the new local git repository, see the [[#Git-svn|git-svn instructions]] and [[#Deficiencies_of_git-svn|its deficiencies]].
Line 820: Line 822:


To share the local developments, the changes can be uploaded to a remote git repository on the SourceForge infrastructure.  For this, a [[#Developer_git_repository|developer git repository]] should first be set up under your SourceForge profile.  Then add this as a remote:
To share the local developments, the changes can be uploaded to a remote git repository on the SourceForge infrastructure.  For this, a [[#Developer_git_repository|developer git repository]] should first be set up under your SourceForge profile.  Then add this as a remote:
<syntaxhighlight lang="bash">
{{#tag:syntaxhighlight|
git remote add origin ssh://<username>@git.code.sf.net/u/<username>/code-<aircraft>
{{repo link|cmd=git remote add|opt=origin|protocol=ssh|login=<username>|user=<username>|type=git|repo=code-<aircraft>|full=1}}
</syntaxhighlight>
| lang = "sh"
}}


And send the master branch where developments are located with:
And send the master branch where developments are located with:
Line 829: Line 832:
</syntaxhighlight>
</syntaxhighlight>


The changes in the new repository will be visible via the web interface at <span style="color: blue"><tt><nowiki>https://sourceforge.net/u/<username>/code-<aircraft>/ci/master/tree/</nowiki></tt></span>.
The changes in the new repository will be visible via the web interface at {{#tag:span|{{#tag:tt|{{#tag:nowiki|{{repo link|user=<username>|repo=code-<aircraft>|branch=master|full=1}}}}}}| style="color: blue"}}.


=== Sending external git repository changes into FGAddon ===
=== Sending external git repository changes into FGAddon ===

Navigation menu