[qt/qtqa/gerrit]: Summary of bulk changes made

KDE Git Services - Bulk Change <[email protected]>
Newsgroups gmane.comp.kde.cvs
Message-ID <[email protected]>
Git repository change summary for qt/qtqa/gerrit
Pushed by mirror-service into branch 'upstream/master'.
Changed from 9e1a8b011adc5e96735cf8eeb2ae7b867914699d to a4a8e113dcd3689cb3107e90ce000b5b2dc49f9c
Acknowledgement was received that this change introduces only existing code that has been pushed to another public open source repository.

This change contains the following new commits:

Git commit a4a8e113dcd3689cb3107e90ce000b5b2dc49f9c by Gerrit Code Review (on behalf of Kaushik Lingarkar) on 24/07/2026 at 00:59..
Update git submodules

* Update plugins/replication from branch 'master'
  to 7e7c2417c7a9cccd6e408955acf271c68c359bb3
  - Allow setting remote.NAME.threads=0 for persist-only mode
    
    Setting 'remote.NAME.threads' to 0 now puts a remote into a
    persist-only mode on the current node. No thread pool is created and
    the node performs no pushes, project deletions or HEAD updates for
    that remote. Replication tasks are still written to the task storage.
    
    This supports multi-primary deployments where a user-facing primary
    only records replication work, while a separate non user-facing
    primary (configured with threads > 0 and distributor enabled) picks
    the tasks up from the shared storage and performs the actual pushes.
    Also, when a node has no push-enabled remotes, both recovery and the
    startup replay are skipped entirely.
    
    A caveat to setting threads to '0' is that project deletions and HEAD
    updates originating on a persist-only node are not replicated by other
    nodes, as they are not persisted to the task storage. If needed, support
    for persisting them can be added in future changes.
    
    Change-Id: I022865cbd7105563b5760ca05ae85847e0d7b97b
https://invent.kde.org/qt/qtqa/gerrit/-/commit/a4a8e113dcd3689cb3107e90ce000b5b2dc49f9c
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.