Fossil SCM
Git backend
e4b91c375851470…
· opened 16 years, 11 months ago
- Type
- Feature_Request
- Priority
- —
- Severity
- —
- Resolution
- Rejected
- Subsystem
- —
- Created
- April 20, 2009 8:56 a.m.
We've had the same idea a long time for making the whole Lumiera project cloneable. When you clone the project, you should get the issue-tracker, the wiki (we're building uWiki for that purpose) and the web page (and of course all the source code).
But we're using Git as many other, and we're extremely pleased with it. But now I see that Fossil also includes (and requires) yet-another-scm. So, how hard would it be to just use parts of the project?
drh added on 2009-04-20 11:33:17:
The version control is not a "backend" on fossil. The version control, the
wiki, and the bug tracking are an integrated whole. It is not feasible to
attach a separate "backend" for a different version control system like Git.
If you like the features of fossil, but are burdened by a Git legacy, I suggest
you work on improving Git by adding to it feature you discovered on fossil.
Failing that, consider writing a tool that will import your git legacy into
a new fossil repository.