This is an automated email from the ASF dual-hosted git repository.
rcordier pushed a change to branch allow-disable-threads
in repository https://gitbox.apache.org/repos/asf/james-project.git
discard 3e38b341e3 This changeset will not alter thread categorisation which
works decently today but only thread presentation to the end user which is
currently relying on search. As an operator I wishes to have a security trigger
if things go blur. [ENHANCEMENT] Allow disable threads
add ba3fe2ad70 [ENHANCEMENT] Allow disable threads
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (3e38b341e3)
\
N -- N -- N refs/heads/allow-disable-threads (ba3fe2ad70)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
.../james/mailbox/postgres/PostgresThreadIdGuessingAlgorithm.java | 6 ++++++
1 file changed, 6 insertions(+)
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscr...@james.apache.org
For additional commands, e-mail: notifications-h...@james.apache.org
