From: vk <g@vkabc.me>
To: git@vger.kernel.org
Subject: [GSoC] Microproject help
Date: Mon, 25 Mar 2024 21:10:03 +0800 [thread overview]
Message-ID: <51647635a10e31e800f87e8bd4a2e62c@vkabc.me> (raw)
Hello all,
I'm Vk and I work as a software engineer. I am interested in
contributing to git repository. Apologies for the late start as I only
stumbled upon GSoC recently and git project interested me as I use it
everyday at work and it would be meaningful for me to contribute to it.
Even if I am not chosen, it will be great if I can start learning to
contribute to git open source.
For the microproject, I have looked into the lists for 2024 and it seems
that all the projects have been taken except for `Replace a
run_command*() call by direct calls to C functions`. However, it seems
that the issue has been solved. The command I ran to search throughout
the repo is `git grep 'run_command*('` and the search result returns
run_command functions which I assume are essential.
If there is any low hanging fruits that you can suggest to me for the
microproject, that will be great. I will also be searching throughout
the mailing list to see if there are any potential microproject to work
on.
Best Regards,
Vk
next reply other threads:[~2024-03-25 13:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-25 13:10 vk [this message]
2024-03-25 18:25 ` [GSoC] Microproject help Karthik Nayak
2024-03-26 11:56 ` vk
2024-03-27 6:36 ` Patrick Steinhardt
2024-03-29 3:57 ` vk
2024-04-02 10:35 ` Patrick Steinhardt
2024-03-29 5:46 ` Junio C Hamano
2024-04-02 9:52 ` Patrick Steinhardt
2024-03-25 20:51 ` Eric Sunshine
2024-03-25 21:23 ` Junio C Hamano
2024-03-25 21:37 ` Eric Sunshine
2024-03-25 21:58 ` Junio C Hamano
2024-03-26 2:59 ` Eric Sunshine
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=51647635a10e31e800f87e8bd4a2e62c@vkabc.me \
--to=g@vkabc.me \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).