On Tue, 28 Feb 2012 07:28:11 -0500 Richard Hipp <d...@sqlite.org> wrote:
> Assuming we go with Fossil 2.0, can somebody propose a list of > interface changes that are needed. We don't want to repeat this > exercise if it can be avoided, so let's fix everything all at once. > Here's a start: > > (1) "fossil rm" removes the files from the disk > (2) "fossil mv" renames the files on disk Those are probably not interface changes, but here are few things I'd like to see in Fossil 2.0: a) Rollback for safe usage when one does not do auto-sync or when code is not pushed out into the wild universe. b) ability to push/pull single branches c) some aliasing mechanism so that user can create aliases for commands invoked with common options, e.g, ability to define cip = ci --private At the moment I cannot think about anything else which I'd like to see in Fossil to have all desired features presented in a superiorly simple package. ;) Stuff like incremental import/export might be handy for those having need to interoperate with other DVCS-es, but probably it's not so easy due to design decisions in Fossil. As far as I am concerned, I'm simply sold on Fossil's simplicity and will use it for our next open-source project and if 2.0 will solve some of the a) - c) items, it would be terrific!!! Sincerely, Gour -- As a strong wind sweeps away a boat on the water, even one of the roaming senses on which the mind focuses can carry away a man's intelligence. http://atmarama.net | Hlapicina (Croatia) | GPG: 52B5C810
signature.asc
Description: PGP signature
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
