20,741
edits
Talk:FlightGear Git on Windows: Difference between revisions
Jump to navigation
Jump to search
→RedLeader's edits (06/2015): new section
(→Error) |
(→RedLeader's edits (06/2015): new section) |
||
| (2 intermediate revisions by one other user not shown) | |||
| Line 19: | Line 19: | ||
** e.g. ''fgfs_win32_vs2010_nightly_2.7.0.exe /S /D=C:\Flightgear\bin\win32'' | ** e.g. ''fgfs_win32_vs2010_nightly_2.7.0.exe /S /D=C:\Flightgear\bin\win32'' | ||
[[User:Macnab|Macnab]] 12:10, 5 November 2012 (EST) | [[User:Macnab|Macnab]] 12:10, 5 November 2012 (EST) | ||
== Regarding "Keeping your FlightGear up to date" and the Git pull command == | |||
Regarding the section "Keeping your FlightGear up to date", the guide seems to be missing or assuming a step. The guide instructs the user to cd to the \data directory, then issue the pull command. But I found that doing so in the \data directory causes Git to download the entire fgdata repository again and stuff the results under \data rather than update \data\fgdata. This can result in some frustration and a big waste of time and bandwidth. | |||
The solution seems to be that the user must cd to \data\fgdata before issuing the pull command. This may be obvious to experienced Git users, but it is not obvious to newbies, especially if they're exactly following this guide to maintain fgdata. | |||
The guide is an otherwise terrific resource and was very helpful. | |||
--[[User:Buckaroo|Buckaroo]] 07:15, 10 February 2013 (UTC) | |||
== RedLeader's edits (06/2015) == | |||
Thanks for doing this, but as you may have noticed, you have not only added new "hard-coded" git links to the article, but also missed a few old ones-so I guess, that it would be really better to introduce separate templates for these purposes, and get rid of any git.sf.net or gitorious.org URLs in general, what do you think ?--[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 15:54, 17 June 2015 (EDT) | |||