Fossil SCM
SVN Import: a better way to migrate from subversion to fossil?
1d5db57881e3842…
· opened 12 years, 3 months ago
- Type
- Code_Defect
- Priority
- —
- Severity
- Important
- Resolution
- —
- Subsystem
- —
- Created
- Dec. 14, 2013 4:04 a.m.
I know, it's not really an code defect, but...
I mean, Fossil SCM is addressed potentially also to SVN users, who do not want GIT but the power of GIT. A direct import from SVN projects without GIT proxy would be nice. You would not have to bother with kurds GIT-stuff and version history would also look better.
Yes, it's a mental thing, but a hurdle.
Line breaks \n in the version history would perhaps also not a bad idea?
Fossil is a really cool SCM, but the migration is not the easiest. :/
Finally of course a thanks for this software. Future users can also make a detour around GIT hopefully soon.
Sorry for my rude tone and bad English. :(
Comments (1)
I know, it's not really an code defect, but...
I mean, Fossil SCM is addressed potentially also to SVN users, who do not want GIT but the power of GIT. A direct import from SVN projects without GIT proxy would be nice. You would not have to bother with kurds GIT-stuff and version history would also look better.
Yes, it's a mental thing, but a hurdle.
Line breaks \n in the version history would perhaps also not a bad idea?
Fossil is a really cool SCM, but the migration is not the easiest. :/
Finally of course a thanks for this software. Future users can also make a detour around GIT hopefully soon.
Sorry for my rude tone and bad English. :(