git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yuting Zheng <05zyt30@gmail.com>
To: git@vger.kernel.org
Subject: [GSoC] Proposal Discussion: git-refs Project
Date: Sun, 23 Mar 2025 21:36:51 +0800	[thread overview]
Message-ID: <CAMvj1+rbYKFNeWEvvN76MTpzfuWc4TN4ViXRE4nTfWy7ZMspWg@mail.gmail.com> (raw)

Dear Git Community,

I am very interested in applying for the GSoC 2025 project "Consolidate
ref-related functionality into git-refs". I have reviewed the relevant
code, documentation, and mailing lists, and as part of the application
prerequisites, I have submitted a microproject patch
(https://lore.kernel.org/git/20250323022111.20226-1-05ZYT30@gmail.com/).

My current idea is to extend the `git-refs` command—by calling into the
existing code—to add subcommands. This approach would replace the
functionalities of the mentioned commands while ensuring that I do not
modify the code underlying them. This guarantees that the new `git-refs`
subcommand meets the new requirements without affecting the usage of the
existing commands.

However, when searching the mailing lists with keywords
“nq:consolidate ref” and “s: refs”, I did not find any discussion about
merging these commands. If anyone has come across any previous discussions
or could kindly provide additional insights on this matter, I would greatly
appreciate your help.

Thank you for your guidance.

Best regards,
Zheng Yuting

             reply	other threads:[~2025-03-23 13:37 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-23 13:36 Yuting Zheng [this message]
2025-03-24 12:02 ` [GSoC] Proposal Discussion: git-refs Project Patrick Steinhardt
2025-03-27  2:26   ` Yuting Zheng
2025-03-28 13:45     ` shejialuo
2025-03-29 14:54       ` Yuting Zheng
2025-03-29 15:02 ` [GSoC] git-refs proposal draft Zheng Yuting
2025-03-31  9:42   ` Patrick Steinhardt
2025-04-01 13:37     ` Yuting Zheng
2025-04-02  8:02       ` Patrick Steinhardt
2025-04-03 15:44   ` Discussion on git-refs list Implementation and Possible Approaches Zheng Yuting
2025-04-04 11:08     ` Karthik Nayak
2025-04-04 15:25       ` Yuting Zheng
2025-04-04 11:15     ` Patrick Steinhardt
     [not found]       ` <CAMvj1+rMY2YR8_GGFeDoJ6HCiVDusZZk9fAguKh=kbctHO=2Qg@mail.gmail.com>
2025-04-04 15:20         ` Fwd: " Yuting Zheng
2025-04-04 15:26       ` Yuting Zheng
2025-04-04 15:16     ` Yuting Zheng
2025-04-06  6:08   ` [GSoC] git-refs proposal v2 Yuting Zheng

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=CAMvj1+rbYKFNeWEvvN76MTpzfuWc4TN4ViXRE4nTfWy7ZMspWg@mail.gmail.com \
    --to=05zyt30@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).