Fossil SCM
Updated my notes tracking the known problems.
Commit
9f297fed37d208ca3ca190043d4a87bf39ff51ff
Parent
a5840849d0e3ceb…
1 file changed
-22
-22
| --- cvs2fossil.txt | ||
| +++ cvs2fossil.txt | ||
| @@ -4,27 +4,5 @@ | ||
| 4 | 4 | |
| 5 | 5 | * Not yet able to handle the specification of multiple projects |
| 6 | 6 | for one CVS repository. I.e. I can, for example, import all of |
| 7 | 7 | tcllib, or a single subproject of tcllib, like tklib, but not |
| 8 | 8 | multiple sub-projects in one go. |
| 9 | - | |
| 10 | -* An internal error thrown when trying to import bwidget of | |
| 11 | - tcllib shows that there have to be some situation I am not | |
| 12 | - handling correctly in the cycle-breaker and sorting passes. | |
| 13 | - | |
| 14 | - It tries to import a changeset on the | |
| 15 | - 'scriptics-sc-2-0-beta-branch' line of development (X), which | |
| 16 | - has no commits yet. So it goes to the parent LOD to get the | |
| 17 | - state we are spawning from. This parent is | |
| 18 | - 'scriptics-sc-1-1-branch' (Y). And is has no changesets | |
| 19 | - committed to it yet. That should not be possible, the ordering | |
| 20 | - constraints should have put all changesets for Y before the | |
| 21 | - changesets of X, and Y had to have at least one changeset, | |
| 22 | - from which the branch could be spawned. | |
| 23 | - | |
| 24 | - This need deep diving into the various linkages to understand | |
| 25 | - what is happening, or not happening, depending. | |
| 26 | - | |
| 27 | - Note: The code I had before more fully tracking the workspace | |
| 28 | - state of the various lods wrongly slid over this problem | |
| 29 | - without erroring out. | |
| 30 | - | |
| 31 | 9 |
| --- cvs2fossil.txt | |
| +++ cvs2fossil.txt | |
| @@ -4,27 +4,5 @@ | |
| 4 | |
| 5 | * Not yet able to handle the specification of multiple projects |
| 6 | for one CVS repository. I.e. I can, for example, import all of |
| 7 | tcllib, or a single subproject of tcllib, like tklib, but not |
| 8 | multiple sub-projects in one go. |
| 9 | |
| 10 | * An internal error thrown when trying to import bwidget of |
| 11 | tcllib shows that there have to be some situation I am not |
| 12 | handling correctly in the cycle-breaker and sorting passes. |
| 13 | |
| 14 | It tries to import a changeset on the |
| 15 | 'scriptics-sc-2-0-beta-branch' line of development (X), which |
| 16 | has no commits yet. So it goes to the parent LOD to get the |
| 17 | state we are spawning from. This parent is |
| 18 | 'scriptics-sc-1-1-branch' (Y). And is has no changesets |
| 19 | committed to it yet. That should not be possible, the ordering |
| 20 | constraints should have put all changesets for Y before the |
| 21 | changesets of X, and Y had to have at least one changeset, |
| 22 | from which the branch could be spawned. |
| 23 | |
| 24 | This need deep diving into the various linkages to understand |
| 25 | what is happening, or not happening, depending. |
| 26 | |
| 27 | Note: The code I had before more fully tracking the workspace |
| 28 | state of the various lods wrongly slid over this problem |
| 29 | without erroring out. |
| 30 | |
| 31 |
| --- cvs2fossil.txt | |
| +++ cvs2fossil.txt | |
| @@ -4,27 +4,5 @@ | |
| 4 | |
| 5 | * Not yet able to handle the specification of multiple projects |
| 6 | for one CVS repository. I.e. I can, for example, import all of |
| 7 | tcllib, or a single subproject of tcllib, like tklib, but not |
| 8 | multiple sub-projects in one go. |
| 9 |