Amebis/WinStd
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update URLs after migration to codeberg.org

Browse Source 
Signed-off-by: Simon Rozman <simon@rozman.si>
This commit is contained in:
Simon Rozman 2024-12-03 10:11:08 +01:00
parent f85047dab9
commit f415b194b5
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@ -78,6 +78,6 @@ void main()
An auto-generated documentation is [here](https://amebis.github.io/WinStd/). An auto-generated documentation is [here](https://amebis.github.io/WinStd/).
More examples and use-cases can be found in [GÉANTLink](https://github.com/Amebis/GEANTLink) and [ZRCola](https://github.com/Amebis/ZRCola) projects source code. They make heavy use of WinStd. Examples can also be found in the `UnitTests` project. More examples and use-cases can be found in [GÉANTLink](https://codeberg.org/Amebis/GEANTLink) and [ZRCola](https://codeberg.org/Amebis/ZRCola) projects source code. They make heavy use of WinStd. Examples can also be found in the `UnitTests` project.
This is a one-man project for the time being, so the Win32 API support is far from complete. It is added as needed. Contributions are welcome. This is a one-man project for the time being, so the Win32 API support is far from complete. It is added as needed. Contributions are welcome.

2
SECURITY.md
View File

@ -10,4 +10,4 @@ The following branches are currently being supported with security updates.
## Reporting a Vulnerability ## Reporting a Vulnerability
Report any vulnerability to [simon.rozman@amebis.si](mailto:simon.rozman@amebis.si). Expect our reply in up to three working days. All confirmed issues will be fixed as soon as possible depending on complexity. After fixed, the security advisory will be published on [the projects security advisory page](https://github.com/Amebis/WinStd/security/advisories). Report any vulnerability to [simon.rozman@amebis.si](mailto:simon.rozman@amebis.si). Expect our reply in up to three working days. All confirmed issues will be fixed as soon as possible depending on complexity. After fixed, the security advisory will be published here.