Issue 3442:Handle commit validation errors when creating/editing changes via REST.
When an exception was thrown by a commit validator during creation ofa new change, or during publish of an inline edit, this resulted in aninternal server error message which did not include the actual reasonfor the error.
Issue 3616:Strip trailing blank lines from commit messages when modified in the inlineeditor.
Blank lines were not trimmed from the end of commit messages, which causedproblems when the commit was merged and then cherry-picked with the -xoption (from the command line).
Tweak JS clipboard API integration to work on Firefox.
The JS copy functionality was working on Chrome, but not on Firefox.
Use image instead of unicode character for copy button.
Some browsers were unable to render the unicode character.
Include server config module in init step.
This allows SecureStore to be used during plugins' init step.
Issue 3659:Show inline comments in change screen history when inline edit is active.
It was not possible to see the inline comments in the history on thechange screen when in edit mode.
Improve rendering of stream-events tasks in the show-queue output.
Entries for stream-events are now rendered as Stream Events (username).
Issue 3655:Fix incorrect owner group matching behavior.
When the given group did not match any group, the group was matchedon a group whose name starts with the argument, instead of throwing anerror to notify the user.
Issue 3664:Fix double slash on URL when switching account.
One too many slashes on the URL caused redirection back to the rootpage instead of the intended location.
Issue 3666:Fix server error when commit validator is invoked on initial commit.
If a commit was uploaded for review as the first commit in a repositorythat was created with no initial empty commit, invoking a commit validatoron the new commit would cause an internal error.
Replication plugin.
Parse replication delay and retry times as time units.
The replication delay and retry values were interpreted as seconds andminutes respectively, but were being parsed as integers.
This is inconsistent with how time units are handled in other Gerritconfiguration settings, and can cause confusion when the user configuresthem using the time unit syntax such as 15s and it causes the pluginto fail with invalid value.
The delay and retry now are parsed as time units. The value can be givenin any recognized time unit, and the defaults remain the same as before;15 seconds and 1 minute respectively.
Remove documentation of obsolete remote.NAME.timeout setting.