mirror of
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
synced 2025-01-03 19:55:31 +00:00
Documentation/process/posting: wrap text at 80 cols
Trivial patch to adjust the text formatting to wrap at 80 columns. No actual content has changed. Signed-off-by: Justin Skists <justin.skists@juzza.co.uk> Signed-off-by: Jonathan Corbet <corbet@lwn.net>
This commit is contained in:
parent
b6e9d06789
commit
f27e1d244b
@ -10,8 +10,8 @@ of conventions and procedures which are used in the posting of patches;
|
|||||||
following them will make life much easier for everybody involved. This
|
following them will make life much easier for everybody involved. This
|
||||||
document will attempt to cover these expectations in reasonable detail;
|
document will attempt to cover these expectations in reasonable detail;
|
||||||
more information can also be found in the files process/submitting-patches.rst,
|
more information can also be found in the files process/submitting-patches.rst,
|
||||||
process/submitting-drivers.rst, and process/submit-checklist.rst in the kernel documentation
|
process/submitting-drivers.rst, and process/submit-checklist.rst in the kernel
|
||||||
directory.
|
documentation directory.
|
||||||
|
|
||||||
|
|
||||||
When to post
|
When to post
|
||||||
@ -198,8 +198,8 @@ pass it to diff with the "-X" option.
|
|||||||
|
|
||||||
The tags mentioned above are used to describe how various developers have
|
The tags mentioned above are used to describe how various developers have
|
||||||
been associated with the development of this patch. They are described in
|
been associated with the development of this patch. They are described in
|
||||||
detail in the process/submitting-patches.rst document; what follows here is a brief
|
detail in the process/submitting-patches.rst document; what follows here is a
|
||||||
summary. Each of these lines has the format:
|
brief summary. Each of these lines has the format:
|
||||||
|
|
||||||
::
|
::
|
||||||
|
|
||||||
@ -210,8 +210,8 @@ The tags in common use are:
|
|||||||
- Signed-off-by: this is a developer's certification that he or she has
|
- Signed-off-by: this is a developer's certification that he or she has
|
||||||
the right to submit the patch for inclusion into the kernel. It is an
|
the right to submit the patch for inclusion into the kernel. It is an
|
||||||
agreement to the Developer's Certificate of Origin, the full text of
|
agreement to the Developer's Certificate of Origin, the full text of
|
||||||
which can be found in Documentation/process/submitting-patches.rst. Code without a
|
which can be found in Documentation/process/submitting-patches.rst. Code
|
||||||
proper signoff cannot be merged into the mainline.
|
without a proper signoff cannot be merged into the mainline.
|
||||||
|
|
||||||
- Co-developed-by: states that the patch was also created by another developer
|
- Co-developed-by: states that the patch was also created by another developer
|
||||||
along with the original author. This is useful at times when multiple
|
along with the original author. This is useful at times when multiple
|
||||||
@ -226,8 +226,8 @@ The tags in common use are:
|
|||||||
it to work.
|
it to work.
|
||||||
|
|
||||||
- Reviewed-by: the named developer has reviewed the patch for correctness;
|
- Reviewed-by: the named developer has reviewed the patch for correctness;
|
||||||
see the reviewer's statement in Documentation/process/submitting-patches.rst for more
|
see the reviewer's statement in Documentation/process/submitting-patches.rst
|
||||||
detail.
|
for more detail.
|
||||||
|
|
||||||
- Reported-by: names a user who reported a problem which is fixed by this
|
- Reported-by: names a user who reported a problem which is fixed by this
|
||||||
patch; this tag is used to give credit to the (often underappreciated)
|
patch; this tag is used to give credit to the (often underappreciated)
|
||||||
|
Loading…
Reference in New Issue
Block a user