From: Junio C Hamano <gitster@pobox.com>
To: Patrick Steinhardt <ps@pks.im>
Cc: Aishwarya Narayanan <aishnana.03@gmail.com>,
git@vger.kernel.org, karthik nayak <karthik.188@gmail.com>
Subject: Re: GSoC 2024 [PATCH]
Date: Wed, 27 Mar 2024 08:23:55 -0700 [thread overview]
Message-ID: <xmqqfrwb4s1g.fsf@gitster.g> (raw)
In-Reply-To: <ZgPrLXjB5mVXitXu@tanuki> (Patrick Steinhardt's message of "Wed, 27 Mar 2024 10:47:25 +0100")
Patrick Steinhardt <ps@pks.im> writes:
> Please not that patches are supposed to be sent as mails directly
> instead of being attached to mails. You can use e.g. git-send-email(1)
> to achieve this.
>
> I would recommend to have a look "Documentation/MyFirstContribution.txt"
> and "Documentation/SubmittingPatches". These resources should get you a
> better picture of how a typical workflow would look like here.
Thanks. It is very good that you recommended the documentation on
the contribution process.
The tasks for microproject are designed to be easy to solve and the
changes in the patches themselves would not be the interesting part
for new contributors. Rather, it is designed for a new contributor
to experience the contribution process from the beginning to the
end, from coming up with an initial patch and explaining it well,
sending it to the list in the established way, receiving and
responding to review comments, and move on to the next iteration.
prev parent reply other threads:[~2024-03-27 15:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-27 9:35 GSoC 2024 [PATCH] Aishwarya Narayanan
2024-03-27 9:47 ` Patrick Steinhardt
2024-03-27 15:23 ` Junio C Hamano [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=xmqqfrwb4s1g.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=aishnana.03@gmail.com \
--cc=git@vger.kernel.org \
--cc=karthik.188@gmail.com \
--cc=ps@pks.im \
/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).