public inbox for git@vger.kernel.org
 help / color / mirror / Atom feed
From: SoutrikDas <valusoutrik@gmail.com>
To: christian.couder@gmail.com
Cc: ayu.chandekar@gmail.com, chandrapratap3519@gmail.com,
	git@vger.kernel.org, jltobler@gmail.com, karthik.188@gmail.com,
	siddharthasthana31@gmail.com, valusoutrik@gmail.com
Subject: Re: [GSOC Proposal] Complete and extend the remote-object-info command for git cat-file
Date: Tue, 17 Mar 2026 18:36:03 +0530	[thread overview]
Message-ID: <20260317130603.84482-1-valusoutrik@gmail.com> (raw)
In-Reply-To: <CAP8UFD3LJEU1YNBOi5VtpZANTY9PA3_v=eU9JF163F2efp-hGg@mail.gmail.com>

Hi there,

> s/has/have/
> s/its/it's/
> s/sreies/series/
> s/type/types/

I will correct all the spelling mistakes.

> > multiple network trips to get a single object's data.
> 
> The `git cat-file` command has a `--batch-command[=<format>]` option
> to enter a command mode. In this command mode some special commands
> and arguments can be passed via stdin to `git cat-file` to request
> information.

Will correct that.

> But anyway I think "information type" is not a good wording for these
> things, because we already talk about "type" for Git object types.
> Please try to find a better wording.

How about object property or object attribute or object field?
I feel like object fields may be a bit more technically correct.

> You can try a rebase to see which issues would need to be resolved to
> complete a rebase, and talk a bit about these issues in your proposal,
> but otherwise applicants shouldn't start working on a project before
> they have been accepted.

I tried a rebase on the current master , and there were indeed conflicts
I will include this part in my v2.


> Would you implement both the client and the server side in the same
> patch series or do it separately?

I am not sure actually... since Eric Ju did everything in one patch series.
But personally I feel like doing one series for server side first and another
for client side would be a bit more focused. But I am not sure if it would
cost more time for everyone involved, like giving feedback and all that?

> > My current semester is ending in the first week of April, so I will be
> > able to contribute 7-8 hours per day, totalling around 35-40 hrs a week
> > on the project.
> 
> Do you have another semester starting after the current one?

Actually I made a mistake, its ending in the first week of May. But no, 
after this semester we have a summer break so ... I will update this part.

> Not sure if that would be very useful first. Also that might be better
> in a different command than `cat-file`.

Alright. I will ask that as a question before my final gsoc proposal
submission so that if its approved, I will add it to my tasks in gsoc.

> There are other ways to do this, like using:
> 
> git rev-list --objects --all --missing=print

Did not know that ... but thats great! I will remove this from the proposal.

Thanks for the feedback.

  reply	other threads:[~2026-03-17 13:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-05 20:48 [GSOC Proposal] Complete and extend the remote-object-info command for git cat-file SoutrikDas
2026-03-15 10:11 ` SoutrikDas
2026-03-16 12:08 ` Christian Couder
2026-03-17 13:06   ` SoutrikDas [this message]
2026-03-16 20:46 ` Karthik Nayak
2026-03-17 15:13   ` SoutrikDas
2026-03-20 13:12 ` [GSoC Proposal v2] " SoutrikDas
  -- strict thread matches above, loose matches on Subject: below --
2026-03-13 10:17 [GSoC] Proposal: " Pablo
2026-03-14  5:58 ` Chandra Pratap
2026-03-14 18:31   ` Pablo
2026-03-15  9:20     ` Chandra Pratap
2026-03-16 11:21     ` Christian Couder
2026-03-16 21:38     ` Karthik Nayak
2026-03-18 10:45       ` Pablo

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=20260317130603.84482-1-valusoutrik@gmail.com \
    --to=valusoutrik@gmail.com \
    --cc=ayu.chandekar@gmail.com \
    --cc=chandrapratap3519@gmail.com \
    --cc=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jltobler@gmail.com \
    --cc=karthik.188@gmail.com \
    --cc=siddharthasthana31@gmail.com \
    /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