version 1.12, 2010/11/09 04:26:51
|
version 1.15, 2010/12/24 10:32:17
|
Line 32 Thus I've tried to simulate working with
|
Line 32 Thus I've tried to simulate working with
|
|
|
For now Fossil lacks some essential features and has other severe problems: |
For now Fossil lacks some essential features and has other severe problems: |
|
|
|
1. Many operations require javascript-capable web browser. |
1. No support for vendor branches. |
1. No support for vendor branches. |
* Redundant to "There's no support for importing vendor source"? |
* Redundant to "There's no support for importing vendor source"? |
* No, it is different. I would import manually, if only some support were there. |
* No, it is different. I would import manually, if only some support were there. |
Line 43 The initial commit is too special, this
|
Line 44 The initial commit is too special, this
|
even "addremove" command isn't in trunk at the time of writing. |
even "addremove" command isn't in trunk at the time of writing. |
* It has been merged to trunk and is part of the pkgsrc version. |
* It has been merged to trunk and is part of the pkgsrc version. |
* No, it isn't part of pkgsrc version at the moment, TIAS. |
* No, it isn't part of pkgsrc version at the moment, TIAS. |
|
* Sorry, you are right. Merged to trunk in [ceab53718f]. |
1. Merge state sticks. You can't undo it. |
1. Merge state sticks. You can't undo it. |
* Not sure what you mean, but "revert" resets the merge state since [d13054ce84]. |
* Not sure what you mean, but "revert" resets the merge state since [d13054ce84]. |
* This is quite recent (late October) fix, I didn't check it. |
* This is quite recent (late October) fix, I didn't check it. |
1. You can't amend your source when you've just merged, you are forced to commit after merge. |
1. You can't amend your source when you've just merged, you are forced to commit after merge. |
* To clarify, the merge has to be committed first, no separate commits are possible from the checkout before that. |
* To clarify, the merge has to be committed first, no separate commits are possible from the checkout before that. |
|
* In practice this makes _critical_ defect in combination of "fossil diff" inability to generate difference for added files. |
1. You can't tune diff command to ignore RCS keywords. |
1. You can't tune diff command to ignore RCS keywords. |
* Since RCS keywords are not really a native command, it is no surprise. An external diff program can be used for this purpose though. |
* Since RCS keywords are not really a native command, it is no surprise. An external diff program can be used for this purpose though. |
|
* Since there's no external diff program that supports it, it is really not quite easy. |
1. You can't diff single file between two given versions. |
1. You can't diff single file between two given versions. |
* diff --from version1 --to version2 path/to/file |
* diff --from version1 --to version2 path/to/file |
* That didn't work, and I'm not sure it works now. It used to ignore path-to-file argument. (It used to bail out when both "--from" and "--to" were used.) |
* That didn't work, and I'm not sure it works now. It used to ignore path-to-file argument. (It used to bail out when both "--from" and "--to" were used.) |
1. There's no way to change commit messages. |
1. There's no way to change commit messages. |
* easily done via ui. |
* easily done via ui: select a commit and under "Other Links" you can find "Edit" (given the necessary permissions). |
* How? It should be possible via command line nevertheless. |
* How? It should be possible via command line nevertheless. |
1. There's no documented way to select commit messages of current branch, or branch by given commit id. |
1. There's no documented way to select commit messages of current branch, or branch by given commit id. |
Or there's a bug preventing it. |
Or there's a bug preventing it. |
* fossil info <commitid> |
* fossil info <commitid> |
* This isn't about "info" command, it is about "timeline" |
* This isn't about "info" command, it is about "timeline" |
|
--> Please clarify what you mean. |
* BTW, this command doesn't support "-R" flag, perhaps you have to check the source out to use it. |
* BTW, this command doesn't support "-R" flag, perhaps you have to check the source out to use it. |
1. Commands are underdocumented, usage messages don't list many available options. |
1. Commands are under-documented, usage messages don't list many available options. |
This applies to trunk at least, there's a branch that states documentation as its goal. |
This applies to trunk at least, there's a branch that states documentation as its goal. |
1. There's no convenient way to look at commit contents: files affected, diff. |
1. There's no convenient way to look at commit contents: files affected, diff. |
* fossil ui and use a web browser |
* fossil ui and use a web browser |
* We don't have web browser in base system, this information should be accessible with command line. |
* We don't have web browser in base system, this information should be accessible with command line. |
|
|
|
|
Some of above problems are reported. |
Some of above problems are reported. |
|
|
Note, all problems above are usability problems, I didn't explore e.g. scalability, |
Note, all problems above are usability problems, I didn't explore e.g. scalability, |
Line 74 Joerg did and had problems, but this is
|
Line 80 Joerg did and had problems, but this is
|
|
|
### Experiences with git |
### Experiences with git |
|
|
please fill in |
Experience with the imported repositories on morden: |
|
- no problem in principle with the smaller modules like othersrc or htdocs (CVS tags are one off but that is expected) |
|
- the large repos are really fragile, and gits idea of how to fix a broken repo seems to be to retrieve a copy from someone/somewhere that happens to not be broken |
|
|
### Experiences with Subversion |
### Experiences with Subversion |
|
|