- May 19, 2024
-
-
[ci:skip-build]: already built successfully in CI
-
- May 17, 2024
-
-
[ci:skip-build]: already built successfully in CI
-
- May 02, 2024
-
-
Clayton Craft authored
-
Clayton Craft authored
-
- Apr 20, 2024
-
-
Newbyte authored
Package was removed.
-
- Apr 11, 2024
-
-
- Apr 02, 2024
-
-
Anton Bambura authored
[ci:skip-build]: already built successfully in CI
-
- Mar 31, 2024
-
-
Ferass El Hafidi authored
Signed-off-by:
Ferass El Hafidi <funderscore@postmarketos.org>
-
- Mar 25, 2024
-
-
Signed-off-by:
Caleb Connolly <caleb@connolly.tech>
-
[ci:skip-build]: already built successfully in CI
-
- Mar 19, 2024
- Mar 18, 2024
-
-
Oliver Smith authored
* Parse the file in python and ensure it is ordered alphabetically * Ensure that we have at least as many gitlab nicknames in CODEOWNERS, as there are listed maintainers in main and community devices. This should help with enforcing that every maintainer is also listed in CODEOWNERS, so they can be easily pinged via their gitlab nickname if something for the device they maintain is happening. [ci:skip-build]: already built successfully in CI
-
Oliver Smith authored
Sometimes we need to figure out the gitlab nicknames of maintainers and co-maintainers as listed in the APKBUILDs, e.g. when a specific issue appears that only happens with a given device. Or if we want to ping all device maintainers in the testing phase for the new release. So far it has been a very tiresome, manual process to figure out gitlab nicknames from the maintainers in the APKBUILDs (involving git log --follow and opening merge requests in browsers...). After some discussion we figured it would be good to store it in the CODEOWNERS file. This also has the nice side-effect that maintainers get notifications if the APKBUILDs they maintain get changed.
-
- Mar 17, 2024
-
-
Oliver Smith authored
-
Oliver Smith authored
We configure editors via editorconfig file. Remove the modeline, it was wrong anyway by setting "et" to expand tabs to spaces, where in reality this file uses tabs.
-
- Feb 11, 2024
-
-
[ci:skip-build]: Already built successfully in CI.
-
- Feb 07, 2024
-
-
Prequisite for dropping DirectFB support from SDL2 builds. Signed-off-by:
David Heidelberg <david@ixit.cz>
-
- Jan 11, 2024
-
-
[ci:skip-build]: Already built successfully in CI.
-
- Jan 10, 2024
-
-
Clayton Craft authored
[ci:skip-build] already built successfully in CI
-
- Dec 29, 2023
-
-
-
Make sure all directories end with a slash, replace spaces with tabs
-
- Dec 23, 2023
-
-
Duje Mihanović authored
[ci:skip-build]: already built successfully in CI
-
- May 23, 2023
-
-
[ci:skip-build] already built successfully in CI
-
- Mar 23, 2023
-
-
Ferass El Hafidi authored
Signed-off-by:
Ferass El Hafidi <vitali64pmemail@protonmail.com>
-
- Mar 10, 2023
-
-
Signed-off-by:
Ferass El Hafidi <vitali64pmemail@protonmail.com> [ci:skip-build]: already built successfully in CI
-
- Nov 29, 2022
-
-
Anton Bambura authored
-
- Nov 27, 2022
-
-
- Nov 26, 2022
-
-
- Nov 02, 2022
-
-
- Oct 18, 2022
-
-
- Oct 16, 2022
-
- Jul 21, 2022
-
-
- May 27, 2022
-
-
Oliver Smith authored
We decided against pvr hacks, quoting craftyguy from issue 1316: > We discussed this in our team meeting, and ultimately decided that > supporting pvr in pmaports/pmOS has many of the same problems that > we saw when trying to support hallium/libhybris, something we > decided against. For much of the same reasons, we've decided that we > want to avoid adding the proprietary userspace components required to > support pvr in pmOS. No device port is using this package anymore, but we forgot to remove it. After branching v22.06 I realized that it doesn't build anymore and as stated in MR 2702, it's unmaintained. Related: https://builds.sr.ht/~postmarketos/job/767700
-
- Mar 30, 2022
-
-
Casey authored
Add myself and Joel as codeowners of SDM845 projects and devices.
-
- Jun 01, 2021
-
-
- Apr 25, 2021
-
-
The entirety of the kde directory was upstreamed to Alpine, so let's remove this to avoid confusion.
-