# HG changeset patch
# User Mads Kiilerich <madski@unity3d.com>
# Date 1365094208 -7200
# Node ID 9855b31d033b6b87bffa791ddbaf245c3ae0b8ac
# Parent  3534e75b2d5bba7f0847499b3daeb94e245aa933
pullrequests: fix changesets ordering being reversed when creating new pull requests

41b4edf77b5b tried to make the displayed order of changeset consistent: The
topmost is always the latest.

That did however also reverse the ordering of the changesets sent back in the
post when used in the pull request creation form. Displaying the pull request
later on would reverse it again and thus show it in the 'wrong' order.

We now undo that reversing when creating the pull requests, and the stored data
will thus be the same as before.

diff -r 3534e75b2d5b -r 9855b31d033b rhodecode/controllers/pullrequests.py
--- a/rhodecode/controllers/pullrequests.py	Fri Apr 05 02:49:26 2013 +0200
+++ b/rhodecode/controllers/pullrequests.py	Thu Apr 04 18:50:08 2013 +0200
@@ -241,7 +241,7 @@
         org_ref = 'rev:merge:%s' % _form['merge_rev']
         other_repo = _form['other_repo']
         other_ref = 'rev:ancestor:%s' % _form['ancestor_rev']
-        revisions = _form['revisions']
+        revisions = reversed(_form['revisions'])
         reviewers = _form['review_members']
 
         title = _form['pullrequest_title']