[Piglit] [PATCH] Add a "Contributing Patches" section to the HACKING file.

[Frank Henigman]

I'd like to see an explanation of "signed-off-by," "reviewed-by" etc.
 Maybe as simple as:

"Use the tags signed-off-by, reviewed-by, tested-by, acked-by as for linux
kernel patches
(see https://www.kernel.org/doc/Documentation/SubmittingPatches)."


On Wed, Nov 13, 2013 at 7:55 AM, Paul Berry <stereotype441 at gmail.com> wrote:

> ---
>
> I received an email this morning asking for information about how to
> contribute to Piglit, and I couldn't find adequate documentation in
> the source tree, so I figured I'd add some more information to the
> "HACKING" file.
>
>  HACKING | 30 ++++++++++++++++++++++++++++++
>  1 file changed, 30 insertions(+)
>
> diff --git a/HACKING b/HACKING
> index d96b994..9eff4ef 100644
> --- a/HACKING
> +++ b/HACKING
> @@ -146,3 +146,33 @@ RELEASE and create an appropriate tag in the git
> repository.
>  This tag is the official way of marking a release, so the tarballs
> provided
>  automatically by the cgit frontend are official release tarballs.
>
> +
> +\ Contributing Patches
> + ---------------------
> +
> +If you want to contribute patches, please subscribe to the piglit
> +mailing list (http://lists.freedesktop.org/mailman/listinfo/piglit)
> +and then send them to piglit at lists.freedesktop.org using "git
> +send-email".  One of the core piglit developers should respond with
> +comments and suggested improvements.  The piglit mailing list is also
> +a good place for general discussion about piglit development, such as
> +future plans for the project, and coordinating work between
> +developers.
> +
> +For developers who are new to piglit: when submitting a patch, it is
> +helpful to add a note (after the "---" line in the patch file)
> +indicating that you are new to the project and don't have commit
> +access; that way once your patch has been revised to meet our
> +standards of correctness and coding style, we will know that we should
> +commit it for you.  If we forget, please remind us!  Once you have
> +successfully contributed a handful of patches, feel free to apply for
> +commit access usind the process described here:
> +http://www.freedesktop.org/wiki/AccountRequests/
> +
> +Please be patient--most of us develop graphics drivers (such as Mesa)
> +as our primary job, so we have limited time to respond to your patches
> +on the piglit mailing list.  If your patch hasn't received a reply in
> +a week, send a follow-up email to make sure we haven't missed it.  If
> +you have questions that are better discussed in real time, many piglit
> +developers can also be found in the #dri-devel channel on Freenode
> +IRC.
> --
> 1.8.4.2
>
> _______________________________________________
> Piglit mailing list
> Piglit at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/piglit
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/piglit/attachments/20131113/4f656519/attachment.html>