On 11/7/15 9:52 AM, Thierry Goubier wrote:
Le 07/11/2015 18:30, Sean P. DeNigris a écrit :
Thierry Goubier wrote
Has it an effect that you loose access to some of the versions of your packages when you delay committing with git + filetree?
I usually just delay the commit in order to save all packages related to a feature, not to save multiple versions of the same package, so I haven't run into that yet.
Hum.
There is this behavior in GitFileTree (saving multiple packages with one commit) but it is only active when you save a package and its dependencies (as in a Slice).
In short, yes, it would be easy to automate if the right concepts and actions were available above the repository. As usual :(
Thierry For tODE, I manage commits and loads, reverts, etc. at the Metacello project level - all dirty packages in a project are committed at once ... you can revert a project and all dirty packages are reverted, merging, etc .... There's a certain amount that can be done through the Metacello api, but I've ended up building a "project model" that wraps Metacello ...
Dale