I'm brand new to fossil but have used git some and mercurial even longer. When I'm working on a project I tend to poke around in the areas of code nearby to what my task directly involves - as a manner of investigating and learning.
The git staging area is useful to my workflow because I am often making changes and testing something, but later decide to have separate commits within all the changes. This helps preserve a nicer history where commits usually have single-responsibility. For example, fixing a null pointer in a button click handler, but also tweaking the button's sizing/border/etc. to be consistent within the UI. I would likely make those two changes at once and test locally, but ultimately have separate commits for each change. On other occasions where I might end up in a similar situations is when finding out one bug is actually multiple bugs. It sounds like fossil is similar to mercurial - mercurial's commit command by default includes all local changes, but arguments can be specified for including/excluding files (or file patterns). When I first started using git I was thrown off by having to include things into staging before committing, but I have started preferring the explicit nature of defining my commits that way. Christopher _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
