Update the master CHANGES file to include 134 #639

wants to merge 1 commit into


None yet

2 participants


Fixes #633

Sinatra member

Will merge later. Having a commit that updates CHANGES after commits that are not yet listed in CHANGES would totally mess with my workflow.


Fair enough, like I said on the other issue, feel free to close and disregard if this doesn't fit with your workflow :) Just trying to be a help :)

@rkh rkh added a commit that referenced this pull request Feb 26, 2013
@rkh rkh update changes, fixes #633 and #639 2d687ab
@rkh rkh closed this Feb 26, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment