Le 06/04/2015 19:37, Yuriy Tymchuk a écrit :
I guess so. Also partially because how monticello works and how
komitter uses it. As far as I understand, Komitter generates a diff,
then you select which changes you want to commit and then it somehow
commits the ancestor with selected changes applied. So if you say
that the actual ancestor in a wrong one and user will deselect some
changes - Komitter will commit the old thing + selected new changes.
Then I don't understand, because:
- git, and gitfiletree, doesn't give a damn about the ancestry. The full
package is written to disk; ancestry and diff is determined later, by
reading from the repository.
- The only thing I could understand would be that komitter shows you the
diff to a given version (say v.X), let you select which changes are
applied, then read the top version from a repo (say v.Y) and apply the
diff to it.
Maybe it’s a problem of Komitter. On the other hand maybe doing it
correctly is too complicated because of how monticello works.
As described, I don't see any difficulty, really.
I'll look into Komitter to see what it does (and how it does it).
Thierry
