On Wed, December 21, 2011 7:31 pm, Mike Meyer wrote: > On Wed, 21 Dec 2011 20:21:18 +0100 > Ramon Ribó <ram...@compassis.com> wrote: > >> > It is not the job of the SCM system to keep in step with my working >> > directory >> Why not? In that case, "fossil update" shouldn't delete files that >> have been removed from repository, but it does. > > Any chance of getting rm/delete's named changed if it's behavior > isn't? "forget", "ignore" or "untrack" are all more descriptive of > what it actually does. > >> > Another issue is that an SCM system is _not_ a backup tool, but many >> > people seem to think that it is. >> Why not? Do you have the truth about what a SCM must and must not do? >> >> One of the nice things about a SCM system is that, in addition to more >> important features, it IS ALSO a backup tool. > > A backup tool stores files for later retrieval. If your SCM doesn't do > that, it's not much of a SCM.
Missing the point entirely. Eric -- ms fnd in a lbry _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
