@@ -229,3 +229,55 @@ For this to work, you need to have your host machine configured to be able to
send e-mail, so that git send-email is able to send mails to the
+++dev@oe-lite.org+++ list. The details for how to do this depends very much
on your host system setup, and is not covered in this handbook.
+
+Single patches
+~~~~~~~~~~~~~~
+
+In some cases creating a pull request will require a lot of work overhead.
+
+When it is figured that a single patch will apply to the master branch
+of a OE-lite repository even after some time this is the faster way to
+submit changes to the project.
+
+Those special cases that applies cleanly could be, e.g. new recipes,
+small changes to split tasks, package tasks and so on.
+
+Let say you made a new recipe and tested it and just committed it
+locally, simply do:
+
+[source,sh]
+----
+git format-patch -1
+----
+
+"-1" may be replaced with a specific commitid or "-2" if you want that
+last two commits in a patchfile.
+
+[source,sh]
+----
+git format-patch -2 mypatches/
+----
+
+Before sending single patch files upstream make sure that you have git
+send-email configure as described above.
+
+If you dont think the log message itself is saying enough to explain
+you change to the other members of the mailing list add
+"--cover-letter" to generate and editable cover letter where you can
+elaborate on the greater meaning with the patch (life, and
+everything).
+
+[source,sh]
+----
+edit mypatch/0000-* #( if coverletter has been chosen)
+git send-email mypatch/*
+----
+
+or just one simple patch:
+
+[source,sh]
+----
+git send-email 0001-<commit log name>.patch
+----
+
+
From: Jacob Kjaergaard <jacob.kjaergaard@prevas.dk> --- upstream.txt | 52 ++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 52 insertions(+)