On Aug 15, 2013 12:00 AM, "Chad Perrin" <[email protected]> wrote: > > On Wed, Aug 14, 2013 at 11:53:41PM +0200, Mark Janssen wrote: > > > > I am curious how auto sync screws with your workflow. I was of the same > > mind in the beginning, always turning of auto sync on my repos. However > > these days I always leave it on, I like the extra automatic backup. > > With a small team, I like being able to make commits locally in fairly > small increments of change, which might leave the project in a broken > state, so I have relatively fine-grained ability to undo changes. When > I get everything to a working state that's ready to share with other > developers, then I push it to the main repository. With autosync turned > on, though, it'll push to the main repo every time I commit something. >
I like to do the same. But even on personal projects I try to keep these kind of experiments in a different branch. Trunk should always build. In a different branch it also easier to back out of mistakes. > -- > Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] > _______________________________________________ > fossil-users mailing list > [email protected] > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
