Le 02/12/2014 20:59, Dale Henrichs a ��crit :
On Tue, Dec 2, 2014 at 11:45 AM, Thierry Goubier
<thierry.goubier@gmail.com <mailto:thierry.goubier@gmail.com>> wrote:
�� �� If you need to update (changes on the central repository), then you
�� �� pull (git pull) and you see the new available versions (only with
�� �� gitfiletree). FileTree will only show you the top version of each
�� �� package.
This is an area where I prefer to use `git diff` and enter the territory
of "git integration"... it is possible to use git to compare two
different SHA's for a given package/project/class/method and it is
possible to compare the in-image package/project/class/method with a
particular.
But both approaches are allowing you that. What GitFileTree shows you is the git commit history, filtered by packages... and you can diff, as well, whether its by package/project/class/method, or simply explore the history from the point of view of the entity your focusing on (well, ok, no project...).
In my opinion, this is the area where one should break from the
Monticello paradigm where the package is the sole versioned entity and
expand the versioned universe to include project/package/class/method
versions. There is also tremendous value to simply comparing two
different git commits which may span multiple packages and include
updates to documentation and other text files ...
Yes, the project on top. I think this is something Phil has been saying as well, and I'm sure this is something which will be added, once Pharo will focus on that.
But I'll check first if some projects (I'm thinking say a compiler of which pharo is just the front-end, i.e. over 100 000lines of which 90% is C code) won't end up being too large. Nothing we can't solve with appropriate tools.
To view git through only the package model is too restrictive and limits
some of the real power one can experience when using git ...
This was the limitation of working within Monticello.
Now that the infrastructure is there, we can (we should) do better.
Thierry