I’m not a bit expert, but if you don’t use “metadataless” format everything works fine with monticello. I.e. each git commit contains all the mc history.
Uko > On 13 May 2017, at 09:28, Thierry Goubier <[email protected]> wrote: > > Le 13/05/2017 à 08:58, Stephane Ducasse a écrit : >> My gut feeling is that it will be better not to mix git and MC. > > It is easy to make MC compatible with Git. > > It wasn't that hard in the past, but needed a community effort (MC being a > core part of the system). Now, with the infrastructure underway (libgit, git > fast-import) it looks very easy to implement. > > Thierry > >> >> >> On Fri, May 12, 2017 at 11:09 PM, Oleksandr Zaytsev >> <[email protected] <mailto:[email protected]>> wrote: >> >> Hello >> >> Two days ago I was trying to send the slice with my fix to PolyMath >> using Monticello. But the version number got set to 1494471195. >> Today I realized that all the packages to which I commit are >> numbered like that. >> >> Cyril Ferlicot explained to me that this happens when I mix git and >> Monticello commits. He suggested that I use a separate image for >> committing to GitHub, or file out/file in if there is a lot of >> changes to commit. >> >> Can this be considered a bug? Should I report it? >> >> I think it would be causing problems for many people. >> >> Oleks >> >> > >
