Timeline for Bringing a large, complex legacy project under git control
Current License: CC BY-SA 4.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 18, 2019 at 0:00 | history | tweeted | twitter.com/StackSoftEng/status/1174110900263038979 | ||
| Sep 17, 2019 at 12:01 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| May 20, 2019 at 11:03 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Apr 20, 2019 at 10:29 | answer | added | Thorbjørn Ravn Andersen | timeline score: 2 | |
| Apr 9, 2019 at 19:17 | comment | added | Dave Tweed | @ThorbjørnRavnAndersen: As I said, past history is just not all that important. What is important is tracking the changes that my client needs to make moving forward. It would be nice (but not a requirement) if they could also capture the changes that have been made to the overall project since it was first delivered to them, which currently exist as a series of "snapshots" of the code tree. | |
| Apr 9, 2019 at 19:09 | comment | added | Thorbjørn Ravn Andersen | You cannot both have tracking of the upstream repositories and a single repository holding the files from all four repositories. You can use submodules to sort of glue all four repositories together but it will most likely not work like you want it to. Would it be an option to have the third party migrate to your new layout? | |
| Apr 9, 2019 at 16:13 | comment | added | Dave Tweed | @ThorbjørnRavnAndersen: The history of the individual subprojects is not important at all -- that can be seen by looking at the original repositories. I'd like to capture the history of the overall project since they were brought together, but that isn't very high on the list of priorities, either. | |
| Apr 9, 2019 at 16:10 | comment | added | Thorbjørn Ravn Andersen | Is the git history important or do you just want to use git from now on? | |
| Apr 9, 2019 at 12:12 | comment | added | Dave Tweed | @ThorbjørnRavnAndersen: From my client's point of view (the OEM of the equipment this software goes into), it's just a single project, and that's how they want to manage it. They don't care or need to know that pieces of it came from different places. They just want to be able to check it out and rebuild it when necessary. | |
| Apr 8, 2019 at 17:36 | comment | added | Thorbjørn Ravn Andersen | Why do you want it in a single repository? Technical/political reasons? | |
| Dec 13, 2018 at 22:25 | review | First posts | |||
| Dec 14, 2018 at 13:54 | |||||
| Dec 13, 2018 at 22:21 | history | asked | Dave Tweed | CC BY-SA 4.0 |