right.. so what you’re saying is once a file is added, its permanently checked out basically, and any changes you make to the file are pending a commit.
> On Aug 15, 2017, at 1:10 PM, Stephan Beal <sgb...@googlemail.com> wrote: > > Nope - that's git's way of doing it (this is why i thought you were using git > as a basis for comparison!). In fossil "add" is a one-time thing which is > only necessary one time (ever) per file. (In git "add" is needed to "stage" > the file for the next commit.) After a file is added, you use "checkin" to > irrevocably commit those changes (along with any number of other changes) to > fossil. There is no intermediary step of "pending for the next commit" in > fossil. Contrariwise, any changes made in a checked-out copy are always > considered "pending for the next commit" (for lack of a better phrase) until > they are either committed or discarded (the checkout is deleted, "close"d, or > otherwise revered to a pristine state). > > -- > ----- stephan beal > http://wanderinghorse.net/home/stephan/ > <http://wanderinghorse.net/home/stephan/> > "Freedom is sloppy. But since tyranny's the only guaranteed byproduct of > those who insist on a perfect world, freedom will have to do." -- Bigby Wolf > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
