Select Git revision
- Branches 20
- pristine-lfs-source
- apertis/v2026dev2 default protected
- pristine-lfs protected
- debian/trixie protected
- upstream/trixie protected
- proposed-updates/debian/sid/ba7bb66e
- apertis/v2025 protected
- apertis/v2025dev1 protected
- apertis/v2025dev2 protected
- apertis/v2025dev3 protected
- apertis/v2025pre protected
- apertis/v2026dev0 protected
- apertis/v2026dev1 protected
- upstream/bookworm protected
- debian/bookworm-backports protected
- apertis/v2024 protected
- apertis/v2024pre protected
- apertis/v2025dev0 protected
- apertis/v2024dev1 protected
- apertis/v2024dev2 protected
- Tags 20
- apertis/0.5.8-1+apertis1
- debian/0.5.8-1
- upstream/0.5.8
- debian/0.5.3-1
- upstream/0.5.3
- apertis/0.4.17-1_bpo12+1+apertis2
- apertis/0.4.17-1_bpo12+1+apertis1
- debian/0.4.17-1_bpo12+1
- upstream/0.4.17
- debian/0.4.15-1_bpo12+1
- upstream/0.4.15
- apertis/0.4.14-4_bpo12+1+apertis2
- apertis/0.4.14-4_bpo12+1+apertis1
- debian/0.4.14-4_bpo12+1
- upstream/0.4.14
- apertis/0.4.13-1+apertis1
- debian/0.4.13-1
- upstream/0.4.13
- apertis/0.4.12-1+apertis1
- debian/0.4.12-1
Search by author
- Any Author
- authors
-
ABHINISH KUMAR abhinish.kumar-ext
- Abhiruchi Gupta abhiruchi
- Akhilesh Dandavati akhilesh.dandavati-ext
- Andre Barkowski andre
-
Andre Moreira Magalhaes andrunko
-
Andrej Shadura andrewsh
- Andrew Lee alee
- Apertis Branching Bot branchingbot
-
Apertis CI robot not_a_robot
-
Apertis rulez checker robot check_rulez_robot
-
Ariel D'Alessandro adalessandro
- Arikkala Vijeth vijeth
- Arnaud Ferraris aferraris
- Baghmar Tarun Tarun.Baghmar
- Balasubramanian Raju raju.balasubramanian-ext
-
Benani Sagar Kishore sagar
- Bindu Shivananda shivananda.bindu-ext
- Chau Doan chau.doanminh-ext
- Christoph Rössig christoph.roessig-ext
-
Christopher Obbard obbardc
- Oct 22, 2020
-
-
modules: refactor dbus reservation · 321545a3Julian Bouzas authored
The Dbus device reservation has been moved into a separate module, and has also been refactored to allow reserving a device name before an actual device is created. Devices now are created and destroyed by the monitor depending on whether PipeWire owns the device or not. This also simplifies a lot the device activation module to always enable devices when they are created, and never worry about checking whether a device is acquired by PipeWire or not.
-
Loading