list mirror (unofficial, one of many)
 help / color / Atom feed
From: Christian Couder <>
To: Оля Тележная  <>
Cc: Thomas Gummerer <>,
	Johannes Schindelin <>,
	git <>, Jeff King <>,
	SZEDER Gábor <>,
	Matthieu Moy <>
Subject: Re: GSoC 2019: Git's application submitted
Date: Mon, 11 Feb 2019 08:45:53 +0100
Message-ID: <> (raw)
In-Reply-To: <>

On Mon, Feb 11, 2019 at 6:48 AM Оля Тележная <> wrote:
> > 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
> > 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.

Great! I thought that it would be a good project for you to mentor and
that's why I added it.

By the way if you would prefer not to mentor the other project I can
remove you from its possible mentor list.

> 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:
> 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.

Do you mean the following comment from

* TODO: add support of %(*raw). Need to switch between oi and oi_deref for that.
* TODO: split logic and printing (as it is done in format_ref_array_item and
* show_ref_array_item). After that we could use %(raw) in all
ref-filter commands.
* TODO: rewrite print_object_or_die so that it will reuse result of general
* oid_object_info_extended call.


It doesn't look like that's it. Could you just copy the task into an
email? Or if you think it could be an idea for a GSoC project, could
you send a pull request to add it to:


> 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?

Yeah, we got en email from Stephanie Taylor saying that our idea list
is quite sparse this year with a link to:

which contains:

"Even if you are a new organization and only want one or two students
showing that you have multiple ideas (a bare minimum of 4 solid ideas)
is vital."

They also want "more detailed description of [each] project (2-5
sentences)", so I think we should work on that too.

So yeah, any help to fix the idea list is very welcome!


  reply index

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-04  9:16 Christian Couder
     [not found] ` <>
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             ` Оля Тележная
2019-02-11  7:45               ` Christian Couder [this message]
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 publically 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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link list mirror (unofficial, one of many)

Archives are clonable:
	git clone --mirror
	git clone --mirror http://ou63pmih66umazou.onion/git
	git clone --mirror http://czquwvybam4bgbro.onion/git
	git clone --mirror http://hjrcffqmbrq6wope.onion/git

Newsgroups are available over NNTP:

 note: .onion URLs require Tor:

AGPL code for this site: git clone public-inbox