From: Eric Frederickson <ericfrederickson68@gmail•com>
To: Lucas Seiki Oshiro <lucasseikioshiro@gmail•com>
Cc: git@vger•kernel.org, Ayush Chandekar <ayu.chandekar@gmail•com>
Subject: Re: A Question from a Hopeful Future Contributor
Date: Sat, 19 Jul 2025 21:02:23 -0400 [thread overview]
Message-ID: <875xfnptcw.fsf@arch.mail-host-address-is-not-set> (raw)
In-Reply-To: <77CAB8BB-ECA5-46FD-A72D-CD59D96B584C@gmail.com>
Lucas Seiki Oshiro <lucasseikioshiro@gmail•com> writes:
>> Hello everyone,
>>
>> I hope that this message finds you well! I'm a software developer and passionate
>> git user, and I'd like to try my hand at contributing to the project.
>
> Hi!
>
> The suggestions from Ayush are really helpful.
Agreed! [1]
> In the last few months I helped some people (a friend and some students from
> my university) to join the Git community and to send their first patches.
>
> I would start with the microproject. Some of them are really easy, but you'll
> get familiar with the contribution process (i.e. sending patches, code
> conventions, commit conventions, etc).
Will do. And I think I've got one in mind :).
> After that, follow the tutorials for creating a new command (MyFirstContribution,
> MyFirstObjectWalk). Perhaps you'll find something outdated in them and that's
> another good opportunity to send another patch!
Noted!
> Another good reference is "First steps contributing to Git" [1]. It covers
> everything that you need to know and to do to get started.
>
> If you aren't familiar with the core concepts of Git (objects, index, references,
> etc), read the chapter "Git Internals" from Pro Git [2].
Both of the resources you linked here are much appreciated.
> I hope it helps you!
Very much so!
> [1] https://matheustavares.dev/posts/first-steps-contributing-to-git
> [2] https://git-scm.com/book/en/v2/Git-Internals-Plumbing-and-Porcelain
Thanks again, and best wishes,
--
Eric Frederickson
ericfrederickson68@gmail•com
https://emfred.com
[1] (I sent him a reply giving my thanks (but forgot to Cc the mailing list...))
next prev parent reply other threads:[~2025-07-20 1:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-18 22:26 A Question from a Hopeful Future Contributor Eric Frederickson
2025-07-18 23:15 ` Junio C Hamano
2025-07-19 19:57 ` Eric Frederickson
2025-07-26 14:21 ` D. Ben Knoble
2025-07-28 15:02 ` Junio C Hamano
2025-07-28 16:54 ` D. Ben Knoble
2025-07-18 23:31 ` Ayush Chandekar
2025-07-19 22:06 ` Lucas Seiki Oshiro
2025-07-20 1:02 ` Eric Frederickson [this message]
2025-07-19 22:16 ` brian m. carlson
2025-07-20 1:22 ` Eric Frederickson
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=875xfnptcw.fsf@arch.mail-host-address-is-not-set \
--to=ericfrederickson68@gmail$(echo .)com \
--cc=ayu.chandekar@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=lucasseikioshiro@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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