Merge branch 'stable-2.10' into stable-2.11
* stable-2.10: Fix various spelling mistakes Prolog-Cookbook: tidy up rule status descriptions Change-Id: I9e2d8b55869f2da7a7e6ff74a6429424dfdc795d
This commit is contained in:
commit
dbe1a5a3c6
Documentation
ReleaseNotes
ReleaseNotes-2.10.1.txtReleaseNotes-2.10.3.txtReleaseNotes-2.10.4.txtReleaseNotes-2.5.txtReleaseNotes-2.8.txt
gerrit-gwtui/src/main/java/com/google/gerrit/client/ui
gerrit-pgm/src/main/java/com/google/gerrit/pgm
gerrit-server/src/main/java/com/google/gerrit/server/project
@ -874,7 +874,7 @@ Suggested access rights to grant:
|
||||
If it's desired to have the possibility to upload temporarily hidden
|
||||
changes there's a specific permission for that. This enables someone
|
||||
to add specific reviewers for early feedback before making the change
|
||||
publically visible. If you want to allow others than the owners to
|
||||
publicly visible. If you want to allow others than the owners to
|
||||
publish a draft you also need to grant them `Publish Drafts`.
|
||||
|
||||
Optional access rights to grant:
|
||||
|
@ -1181,7 +1181,7 @@ much more predictable behavior.
|
||||
Size of the buffer to store logging events for asynchronous logging.
|
||||
Putting a larger value can protect threads from stalling when the
|
||||
AsyncAppender threads are not fast enough to consume the logging events
|
||||
from the buffer. It also protects from loosing log entries in this case.
|
||||
from the buffer. It also protects from losing log entries in this case.
|
||||
+
|
||||
Default is 64 entries.
|
||||
|
||||
|
@ -240,7 +240,7 @@ to the error log:
|
||||
|
||||
----
|
||||
[2012-04-17 14:20:30,558] INFO com.google.gerrit.pgm.shell.JythonShell : Jython shell instance created.
|
||||
[2012-04-17 14:20:38,005] ERROR com.google.gerrit.pgm.shell.JythonShell : Exception occured while loading file Startup.py :
|
||||
[2012-04-17 14:20:38,005] ERROR com.google.gerrit.pgm.shell.JythonShell : Exception occurred while loading file Startup.py :
|
||||
java.lang.reflect.InvocationTargetException
|
||||
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
|
||||
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
|
||||
|
@ -141,15 +141,14 @@ be any other string (see examples below). The `status` is one of:
|
||||
|
||||
* `ok(user(ID))` or just `ok(_)` if user info is not important. This status is
|
||||
used to tell that this label/category has been met.
|
||||
* `need(_)` is used to tell that this label/category is needed for change to
|
||||
become submittable
|
||||
* `reject(user(ID))` or just `reject(_)`. This status is used to tell that
|
||||
label/category is blocking change submission
|
||||
* `impossible(_)` is used when the logic knows that the change cannot be
|
||||
submitted as-is. Administrative intervention is probably required. This is
|
||||
meant for cases where the logic requires members of "FooEng" to score
|
||||
`Code-Review +2` on a change, but nobody is in group "FooEng". It is to hint
|
||||
at permissions misconfigurations.
|
||||
* `need(_)` is used to tell that this label/category is needed for the change to
|
||||
become submittable.
|
||||
* `reject(user(ID))` or just `reject(_)`. This status is used to tell that this
|
||||
label/category is blocking submission of the change.
|
||||
* `impossible(_)` is used when the logic knows that the change cannot be submitted
|
||||
as-is. This is meant for cases where the logic requires members of a specific
|
||||
group to apply a specific label on a change, but no users are in that group.
|
||||
This is usually caused by misconfiguration of permissions.
|
||||
* `may(_)` allows expression of approval categories that are optional, i.e.
|
||||
could either be set or unset without ever influencing whether the change
|
||||
could be submitted.
|
||||
|
@ -23,7 +23,7 @@ LDAP
|
||||
----
|
||||
|
||||
* Several performance improvements when using LDAP, both in the number of LDAP
|
||||
requests and in the amount of data transfered.
|
||||
requests and in the amount of data transferred.
|
||||
|
||||
* Sites using LDAP for authentication but otherwise rely on local Gerrit groups
|
||||
should set the new `ldap.fetchMemberOfEagerly` option to `false`.
|
||||
|
@ -33,7 +33,7 @@ New Features
|
||||
+
|
||||
OpenID auth scheme is aware of optional OAuth2 plugin-based authentication.
|
||||
This feature is considered to be experimental and hasn't reached full feature set yet.
|
||||
Particularly, linking of user identities accross protocol boundaries and even from
|
||||
Particularly, linking of user identities across protocol boundaries and even from
|
||||
one OAuth2 identity to another OAuth2 identity wasn't implemented yet.
|
||||
|
||||
Configuration
|
||||
|
@ -12,7 +12,7 @@ New Features
|
||||
|
||||
* Support identity linking in hybrid OpenID and OAuth2 authentication.
|
||||
+
|
||||
Linking of user identities accross protocol boundaries and from one OAuth2
|
||||
Linking of user identities across protocol boundaries and from one OAuth2
|
||||
identity to another OAuth2 identity is supported.
|
||||
|
||||
* Support identity linking in OAuth2 extension point.
|
||||
|
@ -923,11 +923,11 @@ Eclipse 3 writes a timestamp at the top of these files making the Git
|
||||
working tree dirty. Eclipse 4 (Juno) still overwrites these files but
|
||||
doesn't write the timestamp. This should help to keep the working tree
|
||||
clean. However, since the timestamp is currently present in these
|
||||
files, Eclispe 4 would still make them dirty by overwriting and
|
||||
files, Eclipse 4 would still make them dirty by overwriting and
|
||||
effectively removing the timestamp.
|
||||
+
|
||||
This change removes the timestamp from these files. This helps those
|
||||
using Eclipse 4 and doesn't make it worse for those still using Eclispe
|
||||
using Eclipse 4 and doesn't make it worse for those still using Eclipse
|
||||
3.
|
||||
|
||||
* Add Maven profile to skip build of plugin modules
|
||||
|
@ -625,7 +625,7 @@ Configuration
|
||||
|
||||
* Do not persist default project state in `project.config`.
|
||||
|
||||
* Honor the `gerrit.cannonicalWebUrl` setting when opening the browser after init.
|
||||
* Honor the `gerrit.canonicalWebUrl` setting when opening the browser after init.
|
||||
|
||||
* Fix 'query disabled' error when Query Limit is set.
|
||||
|
||||
|
@ -87,7 +87,7 @@ public class OnEditEnabler implements KeyPressHandler, KeyDownHandler,
|
||||
// Resetting the "original text" on focus ensures that we are
|
||||
// up to date with non-user updates of the text (calls to
|
||||
// setText()...) and also up to date with user changes which
|
||||
// occured after enabling "widget".
|
||||
// occurred after enabling "widget".
|
||||
tb.addFocusHandler(new FocusHandler() {
|
||||
@Override
|
||||
public void onFocus(FocusEvent event) {
|
||||
|
@ -191,9 +191,9 @@ public class JythonShell {
|
||||
+ " is not found or not executable");
|
||||
}
|
||||
} catch (InvocationTargetException e) {
|
||||
log.error("Exception occured while loading file " + p + " : ", e);
|
||||
log.error("Exception occurred while loading file " + p + " : ", e);
|
||||
} catch (SecurityException e) {
|
||||
log.error("SecurityException occured while loading file " + p + " : ", e);
|
||||
log.error("SecurityException occurred while loading file " + p + " : ", e);
|
||||
}
|
||||
}
|
||||
|
||||
@ -204,7 +204,7 @@ public class JythonShell {
|
||||
new Object[] { in, p }
|
||||
);
|
||||
} catch (InvocationTargetException e) {
|
||||
log.error("Exception occured while loading " + p + " : ", e);
|
||||
log.error("Exception occurred while loading " + p + " : ", e);
|
||||
}
|
||||
}
|
||||
|
||||
|
@ -32,7 +32,7 @@ public interface ProjectCache {
|
||||
* Get the cached data for a project by its unique name.
|
||||
*
|
||||
* @param projectName name of the project.
|
||||
* @return the cached data; null if no such project exists or a error occured.
|
||||
* @return the cached data; null if no such project exists or a error occurred.
|
||||
* @see #checkedGet(com.google.gerrit.reviewdb.client.Project.NameKey)
|
||||
*/
|
||||
public ProjectState get(Project.NameKey projectName);
|
||||
|
Loading…
x
Reference in New Issue
Block a user