8,564
edits
FlightGear Git: splitting FGData: Difference between revisions
FlightGear Git: splitting FGData (view source)
Revision as of 18:17, 16 October 2011
, 16 October 2011no edit summary
mNo edit summary |
|||
| Line 17: | Line 17: | ||
The current fgdata developers will have access to every single aircraft repository. In order to maintain aircraft that no longer have an active author, fix global bugs etc. Other users can create merge requests to get their fixes/improvements commited. | The current fgdata developers will have access to every single aircraft repository. In order to maintain aircraft that no longer have an active author, fix global bugs etc. Other users can create merge requests to get their fixes/improvements commited. | ||
== | == Step 1: Split aircraft into seperate repositories == | ||
* You need to have up-to-date fgdata to do this. | * You need to have up-to-date fgdata to do this. | ||
* Expect one aircraft to take 5-30 minutes (depending on the filesizes, number of commits (date of last commit?) etc.). | * Expect one aircraft to take 5-30 minutes (depending on the filesizes, number of commits (date of last commit?) etc.). | ||
| Line 45: | Line 45: | ||
git reflog expire --expire=now --all | git reflog expire --expire=now --all | ||
git gc --aggressive --prune=now | git gc --aggressive --prune=now | ||
== Step 2: Remove all aircraft from fgdata == | |||
Fgdata will be renamed, so we can keep it for some time until we're sure everything is safe. We can then put the "new" fgdata (without all the aircraft data) up. | |||
{{Appendix}} | {{Appendix}} | ||