1) to create the submodule with the full history of the previous commits (see http://will.willandorla.com/extract-to-git-submodule)
2) create a clean repo with only the files from this module (this would make it cleaner, but would preserve the history). Basically the workflow is: create repo in GitHub, clone repo, copy files, commit files, push repo, add submodule
When I did theses tests, the results was that the .git folder for option 1) was 14MB and the .git folder for option 2) was 220Kb
This means that if I do option 1) for each submodule (and there are dozens of them) the size of the overall clone will be massive.
Note: I know there is a way to remove files that are not used from git, but I'm really that inclined to research that now, and figure out how to do it.
Basically they should all be their independent project, each using submodules
The objective is to be able to:
Here are the list of projects to move and their status
* How the refactoring was made
I had two choices here:
1) to create the submodule with the full history of the previous commits (see http://will.willandorla.com/extract-to-git-submodule) 2) create a clean repo with only the files from this module (this would make it cleaner, but would preserve the history). Basically the workflow is: create repo in GitHub, clone repo, copy files, commit files, push repo, add submodule
When I did theses tests, the results was that the .git folder for option 1) was 14MB and the .git folder for option 2) was 220Kb
This means that if I do option 1) for each submodule (and there are dozens of them) the size of the overall clone will be massive.
Since the repo https://github.com/o2platform/FluentSharp is going to keep the history, I'm going to go with option 2.
Note: I know there is a way to remove files that are not used from git, but I'm really that inclined to research that now, and figure out how to do it.