summaryrefslogtreecommitdiff
path: root/docs/patch-policy.txt
diff options
context:
space:
mode:
Diffstat (limited to 'docs/patch-policy.txt')
-rw-r--r--docs/patch-policy.txt12
1 files changed, 10 insertions, 2 deletions
diff --git a/docs/patch-policy.txt b/docs/patch-policy.txt
index b5a585b5e..e948661cf 100644
--- a/docs/patch-policy.txt
+++ b/docs/patch-policy.txt
@@ -10,8 +10,8 @@ While integrating a new package or updating an existing one, it may be
necessary to patch the source of the software to get it cross-built within
OpenADK. OpenADK offers an infrastructure to automatically handle this during
the builds. Patches are provided within OpenADK, in the package directory;
-these typically aim to fix cross-compilation, libc support, or other such
-issues.
+these typically aim to fix cross-compilation, libc support, portability issues
+or other things.
Normally the patches are autogenerated via:
------------
@@ -80,3 +80,11 @@ Fetch from: <some url>
It is also sensible to add a few words about any changes to the patch
that may have been necessary.
+
+Upstreaming patches
+~~~~~~~~~~~~~~~~~~~
+
+OpenADK tries to avoid any patches to the source code. If a patch could
+not be avoided, it should be tried to make the patch of a good quality to
+get it upstream. OpenADK tries to report any found issues and try to send
+in any upstream compatible patches.