From: Hariom verma <hariom18599@gmail.com>
To: ZheNing Hu <adlternative@gmail.com>
Cc: Christian Couder <christian.couder@gmail.com>,
Kaartic Sivaraam <kaartic.sivaraam@gmail.com>,
Git Mailing List <git@vger.kernel.org>, Jeff King <peff@peff.net>,
Junio C Hamano <gitster@pobox.com>,
Shourya Shukla <shouryashukla.oo@gmail.com>,
Emily Shaffer <emilyshaffer@google.com>
Subject: Re: Git in GSoC 2021 ?
Date: Fri, 19 Feb 2021 23:56:43 +0530 [thread overview]
Message-ID: <CA+CkUQ9nK3KyrXTTQifs1eFM-mWiR39Yt_FAbxwfjoiN5CghLg@mail.gmail.com> (raw)
In-Reply-To: <CAOLTT8RAuS5-PgTj4YdvakFV8uA1mfKa-gxBOxnWPcL5Sv0VHg@mail.gmail.com>
Hi,
On Fri, Feb 19, 2021 at 10:39 PM ZheNing Hu <adlternative@gmail.com> wrote:
>
> Hi,Hariom verma,
> I am very glad that you can serve as a possible mentor for GSOC this year!
Yeah, possible co-mentor. Thanks :)
> I am very interested in this "Use ref-filter formats in `git cat-file`".
> Where should I start learning? :)
That's great. Maybe you can start by learning:
- What is cat-file?
- How cat-file works?
- What is ref-filter?
- How ref-filter works?
- What logic previous students came up with to unify these?
- How much work has been done?
Note: here at Git, we usually prefer inline replies. So, please avoid
top posting.
Regards,
Hariom.
next prev parent reply other threads:[~2021-02-19 18:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-16 18:12 Git in GSoC 2021 ? Kaartic Sivaraam
2021-02-17 17:01 ` ZheNing Hu
2021-02-18 23:52 ` Christian Couder
2021-02-19 6:00 ` Hariom verma
2021-02-19 8:47 ` Christian Couder
2021-02-19 10:20 ` Hariom verma
2021-02-19 11:09 ` Christian Couder
2021-02-19 17:08 ` ZheNing Hu
2021-02-19 18:26 ` Hariom verma [this message]
2021-02-20 6:11 ` ZheNing Hu
2021-02-19 14:56 ` Christian Couder
2021-02-19 16:30 ` Kaartic Sivaraam
2021-02-19 17:14 ` Christian Couder
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CA+CkUQ9nK3KyrXTTQifs1eFM-mWiR39Yt_FAbxwfjoiN5CghLg@mail.gmail.com \
--to=hariom18599@gmail.com \
--cc=adlternative@gmail.com \
--cc=christian.couder@gmail.com \
--cc=emilyshaffer@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=kaartic.sivaraam@gmail.com \
--cc=peff@peff.net \
--cc=shouryashukla.oo@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).