When you change a method and save, git will see one file changed (the method) and put it in the commit (there will also be a few changes in the metadata associated with the method and this will be included in the commit, but this won't matter for gitfiletree). Everything else will stay as before, i.e. owned by the original author (if it is done on git). Additionally, the message in the git log will be the one you wrote for the package in MC when saving.
When you start to use git, what you should do is move all your package versions onto the new repository, for example with a Gofer script. It will commit all the versions, starting from the first one, and so recreate the history (but without the merges and resetting timestamps and attributing ownership to you); I don't know enough of git to do a perfect history import, but it could be done. Thierry ________________________________________ De : Pharo-users [pharo-users-boun...@lists.pharo.org] de la part de Paul DeBruicker [pdebr...@gmail.com] Date d'envoi : vendredi 13 septembre 2013 17:47 À : pharo-users@lists.pharo.org Objet : Re: [Pharo-users] FileTree Monticello Repository On 09/13/2013 07:53 AM, Goubier Thierry wrote: > It also bypass most of the stored metadata in the package: methods > timestamps are the git commit timestamps, package history is the git > commit history of the repo (pruned to remove all commits not related to > the package, in the case of a repo containing multiple packages). So does this mean that If I make a bug fix in someone's package and then commit it, I become the author of every method of the package? Or can it tell from the commit that its just that one method that changed and all the other methods are from prior commits? Also, when beginning to use git, if I make the initial commit of the package is all the prior editing and version history lost? Thanks Paul
