On Mon, Jan 11, 2016 at 7:21 PM, Ross Berteig <[email protected]> wrote:
> On 1/11/2016 10:09 AM, Warren Young wrote: > >> 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. >>> >> >> .... >> >> Is there a good argument against making “f branch new” behave like “f >> ci --branch”? >> > > I recall being rather confused by that difference once i have as well, more than once, but... > , and deciding at > the time that f ci --branch was less confusing. that option came much later. Historically, 'branch new' was the way to do it. > 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? >> > i don't have any, but i'm uncreative that way. -- ----- 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 [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
