From: Abhishek Kumar <abhishekkumar8222@gmail.com>
To: hariom18599@gmail.com
Cc: christian.couder@gmail.com, git@vger.kernel.org,
Johannes Schindelin <johannes.schindelin@gmx.de>,
Matheus Tavares Bernardino <matheus.bernardino@usp.br>,
peff@peff.net
Subject: Re: [GSoC][RFC][PROPOSAL v1] Unify ref-filter formats with other --pretty formats
Date: Wed, 26 Feb 2020 13:00:00 +0530 [thread overview]
Message-ID: <CAHk66fszhTMWa14rpupbwDak=t4=svcHr=1CMBBSt8MQbEUqmQ@mail.gmail.com> (raw)
Greetings Hariom,
> Here is the initial version of my proposal. I would really love to
> have comments on it.
> Also, how should I manage the project timeline?
As far as I have seen, there are two approaches to the project timeline.
Some prefer a week by week timeline whereas others have 3-4 week-long
phases instead.
If your work can be neatly divided into a weekly schedule, by all
means - go for it.
> Project title says some past GSoC and Outreachy Interns had worked on this.
> I would also like to be redirected there. So I can learn from there
> work as well.
Olga has worked on migrating the formatting logic from cat-file, log
and for-each-ref to ref-filter as a part of Outreachy 2017-18. Look up
her patches and proposal.
She, along with Christian and Thomas were the possible mentors for last year.
They are the best people to ask to learn from.
Regards
Abhishek
next reply other threads:[~2020-02-26 7:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-26 7:30 Abhishek Kumar [this message]
2020-02-26 16:59 ` [GSoC][RFC][PROPOSAL v1] Unify ref-filter formats with other --pretty formats Hariom verma
-- strict thread matches above, loose matches on Subject: below --
2020-03-23 7:23 [GSoC][RFC][Proposal " Harshit Jain
2020-03-23 9:42 ` Hariom verma
2020-03-23 10:37 ` Harshit Jain
2020-02-26 0:03 [GSoC][RFC][PROPOSAL " Hariom verma
2020-03-04 15:16 ` 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='CAHk66fszhTMWa14rpupbwDak=t4=svcHr=1CMBBSt8MQbEUqmQ@mail.gmail.com' \
--to=abhishekkumar8222@gmail.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=hariom18599@gmail.com \
--cc=johannes.schindelin@gmx.de \
--cc=matheus.bernardino@usp.br \
--cc=peff@peff.net \
/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).