summaryrefslogtreecommitdiffstats
path: root/ReleaseNotes/ReleaseNotes-2.5.2.txt
diff options
context:
space:
mode:
Diffstat (limited to 'ReleaseNotes/ReleaseNotes-2.5.2.txt')
-rw-r--r--ReleaseNotes/ReleaseNotes-2.5.2.txt32
1 files changed, 32 insertions, 0 deletions
diff --git a/ReleaseNotes/ReleaseNotes-2.5.2.txt b/ReleaseNotes/ReleaseNotes-2.5.2.txt
index 76d36d80f4..5e99ebf8ad 100644
--- a/ReleaseNotes/ReleaseNotes-2.5.2.txt
+++ b/ReleaseNotes/ReleaseNotes-2.5.2.txt
@@ -20,6 +20,12 @@ repository had many refs (>100000). Putting existing 'refs/changes/'
or 'refs/tags/' into the RevWalk is now avoided, which improves the
performance.
+* Improve Push performance by discarding 'cache-automerge/*' refs
+ early in VisibleRefFilter
++
+For a typical large Git repository, with many refs and lots of cached
+merges, the push time goes down significantly.
+
* Don't display all files from a merge-commit when auto-merge fails
+
For merge commits Gerrit shows the difference to the automatic merge
@@ -51,6 +57,32 @@ created and as result the change ref that was shown for the new patch
set in the WebUI, and which was contained in the patchset-created
event, was invalid.
+* link:http://code.google.com/p/gerrit/issues/detail?id=1767[issue 1767]:
+ Remove wrong error message when pushing a new ref fails
++
+If pushing a new ref was rejected because the user was not allowed to
+create it the error message always told the user that he's missing the
+'Create Reference' access right. This message was incorrect in some
+cases. Users that have the 'Create Reference' access right assigned
+are e.g. not allowed to create the ref if:
++
+--
+** they are pushing an annotated tag without having the
+ 'Push Annotated Tag' access right
+** they are pushing a signed tag without having the 'Push Signed Tag'
+ access right
+** the project state is set to 'Read Only'
+--
++
+Now the error message just says 'Prohibited by Gerrit'. This generic
+error message is better than a more concrete error message which is
+wrong in same cases because a wrong message is misleading and
+confuses the user.
++
+In addition the description of the 'Prohibited by Gerrit' error in the
+documentation has been updated to explain some additional cases in
+which the 'Prohibited by Gerrit' error occurs.
+
* link:http://code.google.com/p/gerrit/issues/detail?id=1444[issue 1444]:
Remove 'Mailing-List' header from sent emails
+