Le 03/01/2016 17:12, Alexandre Bergel a écrit :
Yes, there is a version number mismatch. But I do not feel this is that important. On some point, version number should be extracted from Git metadata, and not from a simple counter.
I'm solving that (forcing a become to replace the MC version info by the new git generated version info... but the GUI isn't updated). If someone is interested to have a look at refactoring the underlying Monticello model of versions and repositories and caches and ... ;) Thierry
By the way, what is a âsubprocessâ?
Alexandre
On Jan 3, 2016, at 1:04 PM, Mariano Martinez Peck <marianopeck@gmail.com> wrote:
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".
Is there a workaround here so that both could map correctly?
Thanks in advance,
-- Mariano http://marianopeck.wordpress.com