Re: GSoC 2016: applications open, deadline = Fri, 19/2
- From
Christian Couder <christian.couder@gmail.com>
- Date
- Feb 17, 2016, 16:04 UTC
- Message-ID
- <CAP8UFD2OY_QMqvEew5+V+P4653REm_P0R4_JiwwBfo0O6727Xw@mail.gmail.com>
- In-Reply-To
- <alpine.DEB.2.20.1602171353260.6516@virtualbox>
Hi Johannes,
On Wed, Feb 17, 2016 at 2:09 PM, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
Show 8 quoted lines
> >> Then there is also git-bisect.sh with nearly 700 lines, which is also >> not as easy. > > Nothing is easy, but bisect has a much better chance to be finally > converted into a builtin: there is already a bisect--helper builtin, and > all we need to do is to move more parts over, piece by piece. It does not > even have to be a complete rewrite.
I don't know which has a better chance to be finally converted, but it's true that for bisect, the bisect--helper builtin could help, and it can be done piece by piece.
> I count 22 functions with bisect_start and bisect_replay being the obvious > elephants. Personally, I would recommend starting with bisect_next_check > (which would imply get_terms and bisect_voc, of course). It could even be > a mini project for a prospective student.
Not sure it is small enough for a mini project, but sure it is a good choice to start with.
Thanks, Christian.