On Fri, Mar 20, 2015 at 10:26 AM, bch <brad.har...@gmail.com> wrote: > I'm still confused about what "complete" or "split" means in the > contexts that I think people are using this -- > > If I accidentally code two different logical thoughts into a single > file -- and so they are "combined", and uncommitted -- why would tools > or facilities to aid making-discrete two different logical ideas be > discouraged, and what precludes testing this separated code ? >
I think the problem is not everyone is using "test" exactly the same way. If you are talking about automated testing, it can only happen after committing code. If you are talking about developer testing, yes, you can test code after committing it, but ideally you've made changes, tested them, then committed. The staging mechanism seems to require you to make a commit before testing. With git, not so bad. You can rewrite history as much as you want until you're satisfied. With fossil, this doesn't work. Except that it can work in a similarly functional way (yet less confusing from my perspective) as I outlined in my previous email. -- Scott Robison
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
