>It's a matter of taste I agree.
>To me that seems simpler than [ab]using the SCM for that type of thing I think the power of versioning given by the SCM may not be limited to just the publishable code that I write. IMO using it to version other things isn't abusing but realizing its true potential :) On Wed, Dec 16, 2015 at 4:36 PM, Stephan Beal <sgb...@googlemail.com> wrote: > On Wed, Dec 16, 2015 at 11:59 AM, Gaurav M. Bhandarkar < > gaurav.a...@gmail.com> wrote: > >> "git rebase -i" seems to enable me to work on multiple projects at the >> same time. Because of it I can maintain versioned "development sessions" of >> not only my code but other things that were required/relevant to make that >> code. Without it I find it impossible to handle the "context switch" that >> comes when you work on multiple projects. >> > > fossil supports multiple open checkouts of any given repo db copy, which > is arguably a cleaner approach than temporarily sticking stuff into SCM > (when you've no intention of keeping it there). It's a matter of taste, of > course, but fossil does offer an option other than keeping separate trains > of thought in the same physical copy of the tree. To me that seems simpler > than [ab]using the SCM for that type of thing, in particular because a > context switch is a simple 'cd' instead of SCM commands. > > -- > ----- stephan beal > http://wanderinghorse.net/home/stephan/ > http://gplus.to/sgbeal > "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
