I'll take another look right now but I don't recall seeing any "raw" links.
It's at the top-left of the page, in a list of 5 options: main, log, inventory, swap diff, raw.
I also don't see how branching one thing, putting "my" code on top of it, merging the const-fix, then recommitting would be at all easy for those of us who know nothing of how bzr works.
Well, my experience with patch has always been a little, err, patchy. (groan) The workflow with bzr is very easy:
bzr branch (http://... stock 1.9)
move your code on top of it
bzr commit (to make your customized code the current version)
bzr merge (http://... const-fix 1.9)
(deal with conflicts, like in any other VCS, if any arise)
And thinking about it, what code is there to merge? 1.9 hasn't been touched in quite some time, mainly because we were waiting on this fix to be ready but also because as I said, nobody *cough*Kayle*cough* has given me anything ready for adding in anyway.
In your case, dealing with the stock version, I guess there is nothing to merge and you can use the const-fix code exactly as is. I was thinking of people who have their own code bases, because they are doing a three-way merge of sorts:
Const-fix FUSS --- = customized FUSS with const-fix applied
Letting bzr take care of it makes life easier.
Basically, this bzr method lets you easily combine two separate "patches":
stock --> customized
stock --> const-fix
Doing this by hand is painful at best, and so tedious as to be impractical at worst, depending on the size of the changes.