Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

6
  • Why do you want it in a single repository? Technical/political reasons? Commented Apr 8, 2019 at 17:36
  • @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. Commented Apr 9, 2019 at 12:12
  • Is the git history important or do you just want to use git from now on? Commented Apr 9, 2019 at 16:10
  • @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. Commented Apr 9, 2019 at 16:13
  • 1
    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? Commented Apr 9, 2019 at 19:09