On 2013-02-07, at 10:07, Damien Cassou <[email protected]> wrote:
> On Thu, Feb 7, 2013 at 9:54 AM, Camillo Bruni <[email protected]> wrote: >> I just killed all the file-tree noise (mostly metacello version info) >> >> Now we can properly see what changed between pharo versions over all >> packages: >> >> https://github.com/pharo-project/pharo-core/commit/cea99d02a2d0d743880cd7a80a9ded0407bbaf9e >> >> => this will be my major source for debugging information when looking for >> newly introduced bugs! >> => using git-bisect it will be super easy to find these bugs > > > That's really great. What a nice view on the changes. This really > proves we have to leverage existing infrastructure as much as we can. > > Minor comments: > > - would it be possible to ensure all files have a newline character at > the end to avoid this "\ No newline at end of file" everywhere? ha, that's actually a filetree issue ;), I will have to look into it this weekend. In any case I have to cut down the export-times to 7mins again, currently we're at 2h50mins ;) > - can we get meaningful commit messages? it's all still early stage... right now I put the commit messages on the tags. Since technically the commits should be each users changes and you track down changes between each tag/pharo release. but yeah, I should be able to change that for now.
