On Tue, May 14, 2013 at 6:26 PM, Konstantin Khomoutov < flatw...@users.sourceforge.net> wrote:
> mainstream VCSes. But I digress. If memory serves me right, initially > Fossil only supported creation of a branch when committing, and > "explicit" branch creation has been added afterwards, per user requests. > IIRC it was the other way around. i might be wrong, though. i only recently used --branch for the first time, and i've been using fossil a good while, which leads me to suspect that i must have been using the branch/checkout/edit approach. --branch has been there a long time, but i am prone to committing to the wrong branch in that workflow, so i almost never use it. > new line of by *first* creating a branch to work on. People with > a different mindset are fine with first coding something and then > deciding where this should go. There definitely was at least one > thread on this list which discussed this matter, with Richard Hipp > chiming in and explaining he has the mindert of the latter kind ;-) > That's how i remember it. Poking around a little in the repo i just randomly selected a really old version of checkin.c which does not contain the --branch option to the ci command: http://www.fossil-scm.org/index.html/artifact/4a866358e30844ec8501e980dbe2d87f02c34406 But here's from from 2009 which does have it, so it's been around a while: http://www.fossil-scm.org/index.html/artifact/43b7742fd68d09627b40cf44bbeb83ab9fc6c384 -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
