8,567
edits
FlightGear Git: splitting FGData: Difference between revisions
Jump to navigation
Jump to search
FlightGear Git: splitting FGData (view source)
Revision as of 12:24, 17 October 2011
, 17 October 2011Questions
(Questions) |
|||
| Line 54: | Line 54: | ||
The exisiting repository is renamed, and the new repository takes its place and access to the new repository is setup. | The exisiting repository is renamed, and the new repository takes its place and access to the new repository is setup. | ||
The historic fgdata is kept but stays frozen, at least until we're sure everything is safe. It may also be a good idea to keep the existing repo, since it contains release branches - which are not part of the new repository and would be lost otherwise. | The historic fgdata is kept but stays frozen, at least until we're sure everything is safe. It may also be a good idea to keep the existing repo, since it contains release branches - which are not part of the new repository and would be lost otherwise. | ||
== Questions == | |||
* What to do with Aircraft/UIUC should it be placed like "one" aircraft in a aircraft-repository? Or each individual? | |||
** An flightgear-aircraft/UIUC repo has been created, we can delete it if needed later on. | |||
* Gitorious does not support dots in repository names. | |||
** For now we just skipped dots, so Supermarine-S.6B has a repo called <tt>supermarine-s6b</tt> (note that Gitorious also does not distinct capitals). | |||
{{Appendix}} | {{Appendix}} | ||