From: Ammar Faizi <[email protected]>
To: Prince Saini <[email protected]>
Cc: "GNU/Weeb Mailing List" <[email protected]>
Subject: Re: Request for Guidance
Date: Wed, 11 Jan 2023 12:36:53 +0700 [thread overview]
Message-ID: <CAFBCWQJ9pW8sKP8fY4rKCJ3s_-u5m46ufhkN-PcNSOAxS4XMeg@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
On Tue, Jan 10, 2023 at 1:35 AM Prince Saini <[email protected]> wrote:
> Hye,
>
> I want to contribute into open source projects.
> Can you please tell me the resources to grab the technology used by you so that I can contribute properly.
I use the Linux kernel for everyday life. This is the guide to
contributing to the Linux kernel:
https://www.kernel.org/doc/html/latest/process/submitting-patches.html
> Also, please let me know some good first issues to solve.
>
> Hope to hear from you soon.
You can visit the syzkaller dashboard to find issues:
https://syzkaller.appspot.com/upstream
Please don't use an HTML email. Our mailing list rejects HTML emails.
See also: https://people.kernel.org/tglx/notes-about-netiquette
--
Ammar Faizi
parent reply other threads:[~2023-01-11 5:37 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <[email protected]>]
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=CAFBCWQJ9pW8sKP8fY4rKCJ3s_-u5m46ufhkN-PcNSOAxS4XMeg@mail.gmail.com \
[email protected] \
[email protected] \
[email protected] \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox