some (if not all) of the issues were resolved iirc, however since I didn't need to migrate since then I don't know the current status.
�� - a discussion about which process to follow in which conditions
�� �� (should I use GitFileTree or FileTree?)
Please note that GitFileTree didn't reliably work under Windows (problems with ProcessWrapper or something; crashing a lot), don't know the current status.
However from practical standpoint:
* with GitFileTree each MC commit inside Pharo creates a Git commit, so if you change X packages within a single repo, you get also X git commits
* with FileTree you could pack them together more tightly but you need to commit to git explicity.
but otherwise I don't see much practical difference��
- what happens if a Metacello description loads a project hosted in git
�� but I still want to be able to hack on this dependency. So, this
�� dependency should not be read-only for me