jeans/motioneyeos
jeans/motioneyeos
1
0
Fork 0
mirror of https://github.com/motioneye-project/motioneyeos.git synced 2025-07-29 22:26:31 +00:00
Code Issues Packages Projects Releases Wiki Activity

manual: contributing: minor rewording of 'submitting patches' section

Browse Source 
This patch makes some minor changes to the section about submitting patches.
Content-wise there are little changes.

Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>
Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Acked-by: Samuel Martin <s.martin49@gmail.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
This commit is contained in:
Thomas De Schampheleire 2014-03-06 11:07:32 +01:00 committed by Thomas Petazzoni
parent b77143a755
commit 1133097cb2
1 changed files with 11 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
docs/manual/contribute.txt
View File

@ -164,16 +164,18 @@ Submitting patches
_Please, do not attach patches to bugs, send them to the mailing list _Please, do not attach patches to bugs, send them to the mailing list
instead_. instead_.
When your changes are done, and committed in your local git view, If you made some changes to Buildroot and you would like to contribute
_rebase_ your development branch on top of the upstream tree before them to the Buildroot project, proceed as follows. Starting from the
generating the patch set. To do so, run: changes committed in your local git view, _rebase_ your development
branch on top of the upstream tree before generating a patch set. To do
so, run:
--------------------- ---------------------
$ git fetch --all --tags $ git fetch --all --tags
$ git rebase origin/master $ git rebase origin/master
--------------------- ---------------------
Here, you are ready to generate then submit your patch set. Now, you are ready to generate then submit your patch set.
To generate it, run: To generate it, run:
@ -185,7 +187,7 @@ This will generate patch files in the +outgoing+ subdirectory,
automatically adding the +Signed-off-by+ line. automatically adding the +Signed-off-by+ line.
Once patch files are generated, you can review/edit the commit message Once patch files are generated, you can review/edit the commit message
before submitting them using your favorite text editor. before submitting them, using your favorite text editor.
Lastly, send/submit your patch set to the Buildroot mailing list: Lastly, send/submit your patch set to the Buildroot mailing list:
@ -196,9 +198,9 @@ $ git send-email --to buildroot@buildroot.org outgoing/*
Note that +git+ should be configured to use your mail account. Note that +git+ should be configured to use your mail account.
To configure +git+, see +man git-send-email+ or google it. To configure +git+, see +man git-send-email+ or google it.
Make sure posted *patches are not line-wrapped*, otherwise they cannot If you do not use +git send-email+, make sure posted *patches are not
easily be applied. In such a case, fix your e-mail client, or better, line-wrapped*, otherwise they cannot easily be applied. In such a case,
use +git send-email+ to send your patches. fix your e-mail client, or better yet, learn to use +git send-email+.
Cover letter Cover letter
~~~~~~~~~~~~ ~~~~~~~~~~~~
@ -244,7 +246,7 @@ Hereafter the recommended layout:
--------------- ---------------
Patch title less than 80-character length Patch title less than 80-character length
Some more paragraph giving some more details. A paragraph giving more details.
And yet another paragraph giving more details. And yet another paragraph giving more details.