summaryrefslogtreecommitdiff
path: root/Software
diff options
context:
space:
mode:
authorTanuKaskinen <TanuKaskinen@web>2022-07-01 14:57:21 +0000
committerIkiWiki <ikiwiki.info>2022-07-01 14:57:21 +0000
commit2e7ad8d94ecebc4e3f4688c9127699db8cb95ef3 (patch)
treed68d5633dfa37830a424cbc035fa53b0ebaac0c2 /Software
parentd0f631dd9951805597136bb6456ea258bfd38725 (diff)
Diffstat (limited to 'Software')
-rw-r--r--Software/PulseAudio/BugReports.mdwn6
1 files changed, 3 insertions, 3 deletions
diff --git a/Software/PulseAudio/BugReports.mdwn b/Software/PulseAudio/BugReports.mdwn
index fb4f947c..efc57cd4 100644
--- a/Software/PulseAudio/BugReports.mdwn
+++ b/Software/PulseAudio/BugReports.mdwn
@@ -66,12 +66,12 @@ Before posting a bug report you might want to check [[this list of broken ALSA s
If you have an issue with PulseAudio's **mixer handling**, [[read this first|Software/PulseAudio/Documentation/User/PulseAudioStoleMyVolumes]]. If you have an issue with **memory consumption** [[read this first|Software/PulseAudio/Documentation/User/MemoryConsumption]]. If you feel that that PA doesn't honour your **default device** choices, [[read this first|Software/PulseAudio/Documentation/User/DefaultDevice]]. Other **canned responses** [[you find in this list|CannedResponses]].
-## Submitting patches
+<hr>
+# Submitting patches
**Patches** are preferably submitted as a [[Gitlab Merge Request|https://gitlab.freedesktop.org/pulseaudio/pulseaudio/merge_requests]] (this is equivalent to Pull Requests on Github, if you are familiar with those. If not, refer to the [[Gitlab documentation|https://docs.gitlab.com/ee/gitlab-basics/add-merge-request.html]]. Before submitting patches please read through our [[coding style guidelines|Software/PulseAudio/Documentation/Developer/CodingStyle]].
-<hr>
-# Patch Review Status
+## Patch Review Status
We track the submitted patches [[here|https://www.freedesktop.org/wiki/Software/PulseAudio/PatchStatus/]]. That page is updated every two weeks. If you have submitted a patch, and you're waiting for someone to review it, it should be listed on that page (within two weeks). If it's not, then we have missed your patch, in which case please contact the maintainers (for example by sending a mail to the mailing list).