- Appended to comment:
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.
- Appended to comment:
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.
- Appended to comment:
bharder added on 2009-09-29 15:30:17:
reference for "co" alias: a89b436bc9
- Appended to comment:
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). - Change resolution to "Open"
- Change type to "Feature_Request"
- Change comment to "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"
- Change foundin to "20090921191920"
- Change private_contact to "ed6eee22101b988e911a72836c642f206b343b1d"
- Change severity to "Minor"
- Change status to "Open"
- Change title to "replace 'new' with 'init' command for repository creation"
- Change type to "Code_Defect"