textproc/py-sphinxcontrib-programoutput2: import py313-sphinxcontrib-programoutput2-2.0a1
A Sphinx_ extension to literally insert the output of arbitrary commands into
documents, helping you to keep your command examples up to date.
textproc/py-sphinxcontrib-phpdomain: import py313-sphinxcontrib-phpdomain-0.13.2
This package provides a Sphinx extension for documenting PHP projects.
[AMDGPU] Add ML-oriented coexec scheduler selection and queue handling
This patch adds the initial coexec scheduler scaffold for machine
learning workloads on gfx1250.
It introduces function and module-level controls for selecting the
AMDGPU preRA and postRA schedulers, including an `amdgpu-workload-type`
module flag that maps ML workloads to coexec preRA scheduling and a nop
postRA scheduler by default.
It also updates the coexec scheduler to use a simplified top-down
candidate selection path that considers both available and pending
queues through a single flow, setting up follow-on heuristic work.
textproc/p5-Pod-POM-View-Restructured: import p5-Pod-POM-View-Restructured-1.000003
This module outputs reStructuredText that is expected to be used
with Sphinx. Verbatim sections (indented paragraphs) in the POD
will be output with syntax highlighting for Perl code by default.
See "POD commands specifically for reStructuredText" for how to
change this for a particular block.
mail/cyrus-imapd38: import cyrus-imapd-3.8.6
IMAP (Internet Message Access Protocol) is an Internet standards-track
protocol for accessing messages (mail, bboards, news, etc). The Cyrus
IMAP server differs from other IMAP server implementations in that it
is generally intended to be run on "sealed" servers, where normal users
are not permitted to log in. The mailbox database is stored in parts of
the filesystem that are private to the Cyrus IMAP system. All user
access to mail is through the IMAP, POP3, or KPOP protocols.
mail/cyrus-imapd32: import cyrus-imapd-3.2.12
IMAP (Internet Message Access Protocol) is an Internet standards-track
protocol for accessing messages (mail, bboards, news, etc). The Cyrus
IMAP server differs from other IMAP server implementations in that it
is generally intended to be run on "sealed" servers, where normal users
are not permitted to log in. The mailbox database is stored in parts of
the filesystem that are private to the Cyrus IMAP system. All user
access to mail is through the IMAP, POP3, or KPOP protocols.