> It might be better for code review if the old pull is reverted and then this > one re-requested. That will make it easier > to see the real changes.
I count the 1 major merge then 8 commits to fix bugs or tweak things... I just tried reverting them and stopped when I got scared I'll accidentally revert a fix we do want to keep. Instead, I updated my gavinandresen/master github branch to the state of the tree just before the OP_EVAL merge, so for code review purposes you can look at: https://github.com/gavinandresen/bitcoin-git/compare/master...pay_to_script_hash There are unrelated 0.6 pulls in those changes, too, but it should be pretty obvious what is what. -- -- Gavin Andresen ------------------------------------------------------------------------------ Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox _______________________________________________ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
