From: mchehab at kernel.org (Mauro Carvalho Chehab)
Subject: [Linux-kernel-mentees] Patch guidelines and tips
Date: Thu, 27 Jun 2019 06:48:33 -0300 [thread overview]
Message-ID: <20190627064833.3e41d60a@coco.lan> (raw)
In-Reply-To: <6aa42000-1957-b0cf-ae6d-18e89d304892@linuxfoundation.org>
Em Wed, 26 Jun 2019 18:38:31 -0600
Shuah Khan <skhan at linuxfoundation.org> escreveu:
> Mentees,
>
> Thanks for your active participation in working towards the
> required contributions. A few tips and guidelines to make
> this experience productive for us all.
>
> - Before you start working on a task, please check the archive
> first to see if a patch is already in progress. This avoids
> duplicated efforts.
>
> https://lists.linuxfoundation.org/pipermail/linux-kernel-mentees/
>
> - For documentation tasks, start small with picking one file for
> conversion first. You don't have to work on all the files in a
> directory in one step. Working on a single file helps you get
> over the learning curve and then you can take on larger set of
> files as needed.
>
> If in doubt, send email to maintainers - starting with me if you
> prefer.
Please feel free to send e-mail to me with regards to documentation
tasks. I'm open to help with that.
Also, I have a big series of documentation patches under discussion
for the merge process. So, better to check with me before trying to
work on something that was already done.
>
> These steps are all documented on the project page. Don't forget to
> do the following when you send patches:
>
> - Please copy mailing lists and maintainers/developers suggested by
> scripts/get_maintainer.pl
>
> - Please run scripts/checkpatch.pl before sending the patch.
>
> - Compile and test - Documentation compile steps have been documented.
>
> thanks,
> -- Shuah
>
>
>
>
Thanks,
Mauro
WARNING: multiple messages have this Message-ID (diff)
From: mchehab@kernel.org (Mauro Carvalho Chehab)
Subject: [Linux-kernel-mentees] Patch guidelines and tips
Date: Thu, 27 Jun 2019 06:48:33 -0300 [thread overview]
Message-ID: <20190627064833.3e41d60a@coco.lan> (raw)
Message-ID: <20190627094833.oI6uKAqq8VfROe22tNllAGBokhMJLIpVLuhs7mklKzw@z> (raw)
In-Reply-To: <6aa42000-1957-b0cf-ae6d-18e89d304892@linuxfoundation.org>
Em Wed, 26 Jun 2019 18:38:31 -0600
Shuah Khan <skhan at linuxfoundation.org> escreveu:
> Mentees,
>
> Thanks for your active participation in working towards the
> required contributions. A few tips and guidelines to make
> this experience productive for us all.
>
> - Before you start working on a task, please check the archive
> first to see if a patch is already in progress. This avoids
> duplicated efforts.
>
> https://lists.linuxfoundation.org/pipermail/linux-kernel-mentees/
>
> - For documentation tasks, start small with picking one file for
> conversion first. You don't have to work on all the files in a
> directory in one step. Working on a single file helps you get
> over the learning curve and then you can take on larger set of
> files as needed.
>
> If in doubt, send email to maintainers - starting with me if you
> prefer.
Please feel free to send e-mail to me with regards to documentation
tasks. I'm open to help with that.
Also, I have a big series of documentation patches under discussion
for the merge process. So, better to check with me before trying to
work on something that was already done.
>
> These steps are all documented on the project page. Don't forget to
> do the following when you send patches:
>
> - Please copy mailing lists and maintainers/developers suggested by
> scripts/get_maintainer.pl
>
> - Please run scripts/checkpatch.pl before sending the patch.
>
> - Compile and test - Documentation compile steps have been documented.
>
> thanks,
> -- Shuah
>
>
>
>
Thanks,
Mauro
next prev parent reply other threads:[~2019-06-27 9:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-27 0:38 [Linux-kernel-mentees] Patch guidelines and tips skhan
2019-06-27 0:38 ` Shuah Khan
2019-06-27 9:48 ` mchehab [this message]
2019-06-27 9:48 ` Mauro Carvalho Chehab
2019-06-28 8:39 ` sheriffesseson
2019-06-28 8:39 ` Sheriff Esseson
2019-06-28 9:30 ` mchehab
2019-06-28 9:30 ` Mauro Carvalho Chehab
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190627064833.3e41d60a@coco.lan \
--to=unknown@example.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.