Le 03/01/2016 17:04, Mariano Martinez Peck a ��crit :

Hi Thierry,

When I commit from MC, I see the generated commit, with something
like OSSubprocess-MarianoMartinezPeck.7. However, when�� browse the
repository later from MC, I get that such a commit is displayed
as OSSubprocess-MarianoMartinezPeck.4 (the rest of the commit message
maps correctly).

Could this offset be because of the first initial 3 commits? That is,
initial git commit from github, and 2 commits of�� "gitfiletree
repository properties".

This is because Monticello pre-computes a version number without asking the repository about it... And GitFileTree disregard that version number (the 'filetree' metadata) and recomputes a version number from the git log history.

Is there a workaround here so that both could map correctly?

Yes. The latest Pharo5.0 development version of GitFileTree does a become to force Monticello to refer to the git saved version afterwards.

But...

1- The GUI still shows the MC-computed version not the git one :(

2- The package copy stored into package-cache is at the MC version and not the git one.

Maybe there is something to consider there about the model behind Monticello when doing all those operations, especially 2-. At the moment, MC behaves like the package-cache has priority on the specifics of the real repository you are saving to :(