From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Christian Couder <christian.couder@gmail.com>
Cc: "Matheus Tavares Bernardino" <matheus.bernardino@usp.br>,
git <git@vger.kernel.org>,
"Thomas Gummerer" <t.gummerer@gmail.com>,
"Оля Тележная" <olyatelezhnaya@gmail.com>,
"Elijah Newren" <newren@gmail.com>,
"Tanushree Tumane" <tanushreetumane@gmail.com>
Subject: Re: Questions on GSoC 2019 Ideas
Date: Fri, 1 Mar 2019 16:20:16 +0100 (STD) [thread overview]
Message-ID: <nycvar.QRO.7.76.6.1903011611260.41@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <CAP8UFD0jF5k31tBhj=bQMGOJKN8-F-Rx7RXF1SHZ22LEgSo9_Q@mail.gmail.com>
Hi Chris,
On Thu, 28 Feb 2019, Christian Couder wrote:
> On Thu, Feb 28, 2019 at 10:46 PM Matheus Tavares Bernardino
> <matheus.bernardino@usp.br> wrote:
> >
> > I'm also interested in the 'convert script to builtin' task, and I was
> > wondering if 'git-bisect' would be a good candidate for that.
>
> There is an ongoing work on that by Tanushree Tumane, an Outreachy
> intern. The end of the internship is March 5, but it seems to me that
> there is not a lot of work left on the project, and hopefully
> Tanushree or her mentors will take care of that.
By "or their mentors" you are referring to yourself and to myself.
And indeed, there won'y be much to be done to convert the script to a full
built-in. But there were a couple of things that Tanushree also had on
their radar: Fix how git bisect handle many merge bases.
I think that could still be a Google Summer of Code project.
Ciao,
Johannes
>
> Best,
> Christian.
>
> > Thanks,
> > Matheus Tavares
> >
> > [1]: https://public-inbox.org/git/20190226051804.10631-1-matheus.bernardino@usp.br/
>
prev parent reply other threads:[~2019-03-01 15:20 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-28 21:46 Questions on GSoC 2019 Ideas Matheus Tavares Bernardino
2019-02-28 22:07 ` Christian Couder
2019-03-01 9:30 ` Duy Nguyen
2019-03-02 15:09 ` Thomas Gummerer
2019-03-03 7:18 ` Christian Couder
2019-03-03 10:12 ` Duy Nguyen
2019-03-03 10:17 ` Duy Nguyen
2019-03-05 4:51 ` Jeff King
2019-03-05 12:57 ` Duy Nguyen
2019-03-05 23:46 ` Matheus Tavares Bernardino
2019-03-06 10:17 ` Duy Nguyen
2019-03-12 0:18 ` Matheus Tavares Bernardino
2019-03-12 10:02 ` Duy Nguyen
2019-03-12 10:11 ` Duy Nguyen
2019-04-04 1:15 ` Matheus Tavares Bernardino
2019-04-04 7:56 ` Christian Couder
2019-04-04 8:20 ` Mike Hommey
2019-04-05 16:28 ` Matheus Tavares Bernardino
2019-04-07 23:40 ` Christian Couder
2019-03-05 23:03 ` Matheus Tavares Bernardino
2019-03-06 23:17 ` Thomas Gummerer
2019-03-03 10:03 ` Duy Nguyen
2019-03-03 16:12 ` Thomas Gummerer
2019-03-01 15:20 ` Johannes Schindelin [this message]
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=nycvar.QRO.7.76.6.1903011611260.41@tvgsbejvaqbjf.bet \
--to=johannes.schindelin@gmx.de \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=matheus.bernardino@usp.br \
--cc=newren@gmail.com \
--cc=olyatelezhnaya@gmail.com \
--cc=t.gummerer@gmail.com \
--cc=tanushreetumane@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.