On Jan 11, 2016, at 7:14 AM, Stephan Beal <[email protected]> wrote: > > i just got an off-list chat question regarding fossil not switching branches > when a new one is created.
Fossil does automatically switch you to the new branch if you create it via f ci --branch. I find that to be a better way to create branches anyway, because I find that by the time I realize I need a new branch, I have changes-in-progress which I’m unwilling to check into the existing branch. > f branch new NAME > > "should" output a message like: > > To switch to the new branch, use one of > > $fossil co NAME > or > $fossil up NAME Is there a good argument against making “f branch new” behave like “f ci --branch”? Obviously there’s the inertia of existing practice, but I wonder how many people that would affect. What use case exists where you *want* to create a new branch but not switch to it immediately? _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
