2015-09-09 16:43 GMT+02:00 Peter Uhnák <i.uh...@gmail.com>: > - a discussion about moving a smalltalkhub repository to git while >> preserving history > > > I've migrated some time ago > > http://forum.world.st/moving-to-git-and-preserving-monticello-history-td4806386.html > > 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. >
I don't either. I made some changes on the ProcessWrapper use, hoping for the best, but I can't test :( > 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. > Dale has the idea of a project (grouping packages) with a single commit; however the MC API has no notion of committing multiple packages in one step except when dealing with dependencies. GitFileTree, for handling package dependencies, has a mode for writing multiple packages and commit only once, so one commit for multiple packages would be very easy to do. A special api for Versionner? Thierry
