Howto:Build and run FlightGear on Raspberry Pi 4: Difference between revisions

Jump to navigation Jump to search
Line 708: Line 708:


Link to <code>git</code> [https://www.git-scm.com/book/en/v2/Customizing-Git-Git-Configuration configuration and customization] information page.
Link to <code>git</code> [https://www.git-scm.com/book/en/v2/Customizing-Git-Git-Configuration configuration and customization] information page.
Florent wrote:
<blockquote>
I'm not knowledgeable about details of the RaspBerry PI build; what I can
say regarding your message is: when you clone a Git repository with no
special option such as --bare, some branch is initially checked out (often,
this is 'master'). This means that only this particular branch is clearly
visible in the directory where the repository has been cloned. Other
branches may be present in hidden/machine form inside the .git subdirectory
after you do 'git fetch foo', where foo is the name of a <s>branch</s>.
Run 'git branch -r' to see what branches are available remotely, then 'git
fetch foo' to retrieve the <s>branch</s> you are interested in (supposedly called
'foo' here). This only happens in the .git subdirectory, but then 'git
checkout foo'  should cause this branch to appear in the filesystem,
replacing whatever was previously checked out in your clone of the upstream
repository. In the case of the download_and_compile.sh script,
OpenSceneGraph-3.4 is the name of the OSG branch currently used by the
script (until a newer version is deemed preferable). Note that as a safety
measure, you can't check out a different branch when there is “unfinished
work” (things modified but not committed) on the currently checked-out
branch.
Hope this helps. Regards
I have to correct something from my first reply in this thread:
The argument passed to 'git fetch' is not branch name (according to
the manual, it's a <refspec>). The way I use this command is by
passing a remote name, e.g. 'git fetch origin' or 'git fetch
upstream'. A “remote” is some place where the repository is hosted
that is known to your clone (.git/config). Thus, your clone can fetch
branches and commits from remotes. A remote can offer many branches.
You can display info about known remotes with 'git remove -v' from
within your clone, but I believe this info essentially comes from the
.git/config file.
<blockquote>


===Copy Path(s)===
===Copy Path(s)===
320

edits

Navigation menu