THierry

https://github.com/pharo-project/pharo/pull/1208 This means a change in the FileTree code. No test case in the Pharo pull request.

Example: I have two packages in FileTree: issue136-2.package/ and issue136-2.v3.package/ For Gofer, issue136-2.v3 is a correct answer for a request for issue136-2

instead of version numbers, and show all branches... Experimental.

Implement a MCDiff-based FileTree writer to accelerate writing large package to disk. Starting point: pharo5.0_dev.

John Brant suggested a fix to gitfiletree use of OSProcess on Mac OS/X. It seems to do no harm on Linux.

Trying to backport issue #124 in the pharo2_dev branch. Will try a merge by Monticello :)

Add the ability for FileTree to handle metadata-reduced packages

4

When reading a package, gitfiletree skips monticello.meta/version and methodProperties.json, so those files could be removed (and then we would get rid of git merge conflicts !). However FileTree is not...

Update tests package versions to track git state

7

Would it be possible to push new versions of the test packages to make sure they are coherent with their version metadata ? Test packages for issues 72 and 33...

MCFileRepositoryInspector>>refresh should be an override

11

MCFileRepositoryInspector>>refresh is defined as belonging to MonticelloGUI (MarcusDenker.213) and in MonticelloFileTree-Core there is a different version. Should the refresh in MonticelloFileTree-Core be put as an override (i.e. in category *monticellofiletree-core-override...

Proposal: add the ability to extract version information from repository url

1

For baselines. In the Metacello registry, baselines are listed as 'no version' compared to configurations where a version can be listed (when one prints the registration). Given that, for baselines,...