git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: JAYATHEERTH K <jayatheerthkulkarni2005@gmail.com>
To: git@vger.kernel.org
Subject: [GSOC] Machine-Readable Repository Information Query Tool
Date: Sun, 23 Mar 2025 20:20:18 +0530	[thread overview]
Message-ID: <CA+rGoLdvY+JdgdzgE04EJoF9KGUpd39+2S_AgpFyucP38mdFgA@mail.gmail.com> (raw)

With GSoC proposal submissions starting tomorrow, I’d like to
understand more about the procedure.

As part of my microproject, I worked on modifying tutorials where we
create new Git commands[1]. I also have strong experience with C and
Shell Scripting and would like to contribute by developing a dedicated
command to fulfill what git-rev-parse was originally intended for.

Could you provide more details on how to proceed?

[1] - https://lore.kernel.org/git/20250321143022.5406-1-jayatheerthkulkarni2005@gmail.com/T/#u

Thank you,
Jay

             reply	other threads:[~2025-03-23 14:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-23 14:50 JAYATHEERTH K [this message]
2025-03-24 11:57 ` [GSOC] Machine-Readable Repository Information Query Tool Patrick Steinhardt
2025-03-24 13:17   ` JAYATHEERTH K

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=CA+rGoLdvY+JdgdzgE04EJoF9KGUpd39+2S_AgpFyucP38mdFgA@mail.gmail.com \
    --to=jayatheerthkulkarni2005@gmail.com \
    --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).