On Mar 4, 2015, at 1:59 PM, bch <brad.har...@gmail.com> wrote: > > What you're describing here is the crux of the problem, and I think > can be fairly described as separation of concerns -- the domain of > the version control is it's controlled files, and if a file is not > handled by version control, (ie: fossil rm somefile), should fossil be > reaching outside of its area of responsibility, well-intentioned or > not ?
Many filesystems and OSes combine file versioning and file management: https://en.wikipedia.org/wiki/Versioning_file_system In a sense, VCSes are a way to get such features on top of filesystems that lack these abilities. Before you reject the idea of one-step rm totally, work your way through the table documenting Mercurial’s approach: http://www.selenic.com/mercurial/hg.1.html#remove Do you see a problem if Fossil worked that way, too? _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
