Fossil SCM

The repository is created with command:

fossil new DIR

Please change this command to

fossil init DIR

Which is in use of the 90% of the existing version control software. This would help to keep fossil familiar to other users. Different command terminology is in many times confusing when different tools are switched.

Please also review other commands, like:

fossil open => fossil checkout (and alias "co") fossil timeline => fossil log fossil leaves => fossil branches (?)

Jari

bharder added on 2009-09-29 15:26:59:
Setting up "aliases" for the requested commands can be considered, as has been done in the past (see my own "co" command).

bharder added on 2009-09-29 15:30:17:
reference for "co" alias: [a89b436bc9]

anonymous claiming to be Dmitry Chestnykh added on 2009-10-11 13:01:44:
I don't think it's a good idea to rename "new" to "init".

Firstly, I don't see why "init" describes creation of a new repository better than "new".

Secondly, "new" is actually different from "init" in Git or Mercurial, because it creates an SQLite file for repository, not a dot-folder inside the specified directory, so renaming it to "init" can be misleading. Also, it requires a name of the repository file, not directory.

anonymous added on 2009-12-18 21:52:24:
Another thing to consider is after you create a "new" repository you still have to run "fossil open xxx" to actually start working in the repo. I would think that "new" should go ahead and "open" the repo.

anonymous added on 2010-11-08 11:27:32: I agree that fossil should provide "init" as alias to "new" at least.
Common usage is "VCS init /path/to/repository".
Whether repository is a directory or a DBMS doesn't matter here.

dmitry added on 2011-09-08 21:53:24 UTC: Fossil accepts both 'new' and 'init' as of [21880ca1b6].