doc: Describe how to send patches.

* doc/cuirass.texi (Contributing): Describe how to send patches.
improve-build-parallelism
Mathieu Lirzin 2017-01-29 18:05:58 +01:00
parent 4d1f2d989d
commit f695c79eb3
No known key found for this signature in database
GPG Key ID: 0ADEE10094604D37
1 changed files with 16 additions and 1 deletions

View File

@ -196,7 +196,22 @@ Display an help message that summarize all the options provided.
@chapter Contributing
Everyone is welcome to contribute to Cuirass. You can report bugs, send
patches and share your ideas at @email{bug-cuirass@@framalistes.org}.
patches and share your ideas with others by sending emails the
@email{bug-cuirass@@framalistes.org, mailing list}.
Development is done using the Git distributed version control system.
Thus, access to the repository is not strictly necessary. We welcome
contributions in the form of patches as produced by @code{git
format-patch}. Please write commit logs in the ChangeLog format
(@pxref{Change Logs,,, standards, GNU Coding Standards}); you can check
the commit history for examples.
When posting a patch to the mailing list, use @samp{[PATCH] @dots{}} as
a subject. You may use your email client or the @command{git
send-email} command. We prefer to get patches in plain text messages,
either inline or as MIME attachments. You are advised to pay attention
if your email client changes anything like line breaks or indentation
which could potentially break the patches.
@c *********************************************************************
@node GNU Free Documentation License