On Tue, Aug 9, 2011 at 4:58 PM, Richard Hipp <d...@sqlite.org> wrote:
> That seems like so much more trouble. What am I missing? Is it that > people are unaware that they can make edits that are destined to go into a > branch before that branch actually > In my experience it's that when i know i've reached a branch point i clean up my trunk, get it comitted, create the branch, and continue work from there. i don't "spontaneously trunk", though i'm sure many do. > Part of the motivation for this question is that, because I never use > "fossil branch new" myself, there tend to be more bugs in that command than > in the other commands that I use daily. If there is a good reason to do > "fossil branch new" then maybe I'll start using it myself and those bugs > will get fixed sooner. Or if not, maybe I'll deprecate "fossil branch new" > - or at least print a warning and ask for confirmation: "Creating branches > ahead of check-ins is unnecessary. Are you sure you want to do this? (y/N)" > i would be really annoyed by such a question - it's a perfect example of software trying to go too far in its assumptions. > Please explain. Thanks! > It's simply a different way of doing it. -- ----- stephan beal http://wanderinghorse.net/home/stephan/
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
