From: "Оля Тележная" <olyatelezhnaya@gmail.com>
To: Thomas Gummerer <t.gummerer@gmail.com>
Cc: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
"Christian Couder" <christian.couder@gmail.com>,
git <git@vger.kernel.org>, "Jeff King" <peff@peff.net>,
"SZEDER Gábor" <szeder.dev@gmail.com>,
"Matthieu Moy" <Matthieu.Moy@gmail.com>
Subject: Re: GSoC 2019: Git's application submitted
Date: Mon, 11 Feb 2019 08:41:18 +0300 [thread overview]
Message-ID: <CAL21Bmkkpzp7fhAnjstTjeH+unDFk8-uhFAgKFfuczYzejf2RA@mail.gmail.com> (raw)
In-Reply-To: <20190207213326.GF6085@hank.intra.tgummerer.com>
> It would be nice to have a few more project ideas.
I am not sure I have additional ideas for 3-month project for the intern, but
> https://git.github.io/SoC-2019-Ideas/ currently lists only 2 possible
> projects:
>
> - Unify ref-filter formats with other --pretty formats (which is new)
I am ready to act as a mentor in this task, I know that part of
project good enough.
I have additional related task: We have a function called
oid_object_info, it allows to download meta-info of the file. It was
used in cat-file, and inspired by that example, I improved ref-filter,
so now ref-filter works faster with it. Moreover, I have found that
oid_object_info allows to get the contents of the file. It was useful
in ref-filter, and actually it could be also useful in cat-file, but
we still download the file differently in cat-file, and it looks
awkward. I need to make just one last move to finish my patch: it will
close the task about migrating cat-file formatting logic to
ref-filter. But cat-file still will not use general way to download
the file. So, the task is to get rid of additional file-reading logic.
I guess this task is much smaller than original one, but at least the
student will have chance to finish it in 3 months.
My patch is here: https://github.com/git/git/pull/568
But I hope you will also see it this week in the mailing list.
Proposed task is in TODO in the end of ref-filter file.
By the way, we had a letter from Google, it is said that our tasks are
sparsed. I am not sure I understand it correctly. Should I help the
project somehow to solve our issues?
next prev parent reply other threads:[~2019-02-11 5:49 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-04 9:16 GSoC 2019: Git's application submitted Christian Couder
[not found] ` <CAL21Bm=K6zZ=APkiP3A_X7xVoOfx-MY2435YMp5y1ztE-xyYtg@mail.gmail.com>
2019-02-04 12:54 ` Christian Couder
2019-02-04 21:52 ` Thomas Gummerer
2019-02-05 21:17 ` Thomas Gummerer
2019-02-05 22:00 ` Christian Couder
2019-02-06 22:09 ` Thomas Gummerer
2019-02-07 19:39 ` Johannes Schindelin
2019-02-07 21:33 ` Thomas Gummerer
2019-02-11 5:41 ` Оля Тележная [this message]
2019-02-11 7:45 ` Christian Couder
2019-02-11 8:31 ` Оля Тележная
2019-02-11 10:52 ` Christian Couder
2019-02-13 22:36 ` Elijah Newren
2019-02-14 9:48 ` Christian Couder
2019-02-11 8:35 ` Christian Couder
2019-02-11 22:18 ` Thomas Gummerer
2019-02-11 23:58 ` Christian Couder
2019-02-12 20:25 ` Thomas Gummerer
2019-02-12 20:49 ` Christian Couder
2019-02-12 22:13 ` Thomas Gummerer
2019-02-06 12:27 ` Johannes Schindelin
2019-03-05 12:04 ` Duy Nguyen
2019-03-05 12:23 ` Duy Nguyen
2019-03-06 4:49 ` Jeff King
2019-03-06 9:36 ` Duy Nguyen
2019-03-06 19:08 ` Jeff King
2019-03-06 14:16 ` Johannes Schindelin
2019-03-18 12:51 ` Duy Nguyen
2019-03-18 16:37 ` 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=CAL21Bmkkpzp7fhAnjstTjeH+unDFk8-uhFAgKFfuczYzejf2RA@mail.gmail.com \
--to=olyatelezhnaya@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=Matthieu.Moy@gmail.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=szeder.dev@gmail.com \
--cc=t.gummerer@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).