An arrow story
Well, a few weeks ago someone posted some comments from the Mercurial folks about our (and Git's) recursive merge strategy. I covered it a few days ago here.Interestingly, some people argued that the way in which we render the branches in the branch explorer (merge links pointing from source to destination) is not correct. I really don't care about how correct it is since I don't feel like teaching graphs theory on a daily basis, but we do always listen :P.
This is basically how the Branch Explorer renders branches and commits (changesets):
And well, in Plastic SCM 4.1 (it is ready down here and soon will be published under "labs" for the impatient among you) there's a hacker hidden option:edit branchexplorer.cfg and add: display.options.dag_mergelinks=trueand then you'll see:
Which, ok, well, whatever, I guess it has its own audience! :P
Vertical
4.1 features the long awaited, begged, proposed and requested "2D version tree feature" that I'm not unveiling today... :P And together with it it comes the possibility to render your branch explorer... vertically... up means newer.All credits to Mr. Daniel Peñalba! :P
Enjoy!
You're welcome :-P
ReplyDelete