From: Hazem Alrawi <hazemalrawi7@gmail.com>
To: Kristoffer Haugsbakk <code@khaugsbakk.name>
Cc: git@vger.kernel.org
Subject: Re: Newcomer
Date: Thu, 22 Jun 2023 18:58:54 +0300 [thread overview]
Message-ID: <CAJf_aa1WF_fKeb2JJ9CnQiEthx4YE9KD8fuD1Q09aX3n2UbMYQ@mail.gmail.com> (raw)
In-Reply-To: <43c88a0d-2f35-4a9f-a6e9-a32360dfe42c@app.fastmail.com>
Hello,
I've already gone through this tutorial so please feel free to assign
me any good-first-issues that will help me to explore Git much more
better.
On Mon, Jun 12, 2023 at 10:25 AM Kristoffer Haugsbakk
<code@khaugsbakk.name> wrote:
>
> Hi
>
> On Mon, Jun 12, 2023, at 04:45, Hazem Alrawi wrote:
> > Hello,
> > My Name is Hazem Alrawi, CS student
> > I want to deep dive into git codebase and begin contributing to open
> > source but I encountered some problems and I have no idea how to solve
> > them, so can you please guide me to fully understand what's going on?
> > here is my prior background
> > -C++
> > -Data structures
> > -Algorithms
> > -OOP
> > I used to solve Problems on different platforms like Codeforces and leetcode
> > Codeforces Handle:HazemRawi
> > LeetCode Username:HazemRawi
> > I've solved more than 1500 problem on different algorithms and DS (You
> > will find them listed on leetcode account)
> > What is the prerequisite I have to learn in order to start fixing bugs
> > and begin contributing to open source projects like git?
>
> Here’s a tutorial: https://git-scm.com/docs/MyFirstContribution
>
> --
> Kristoffer Haugsbakk
prev parent reply other threads:[~2023-06-22 15:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-12 2:45 Newcomer Hazem Alrawi
2023-06-12 7:24 ` Newcomer Kristoffer Haugsbakk
2023-06-22 15:58 ` Hazem Alrawi [this message]
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=CAJf_aa1WF_fKeb2JJ9CnQiEthx4YE9KD8fuD1Q09aX3n2UbMYQ@mail.gmail.com \
--to=hazemalrawi7@gmail.com \
--cc=code@khaugsbakk.name \
--cc=git@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).