git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: GSoC Project | Improvise git bisect

From
Pranit Bauva <pranit.bauva@gmail.com>
Date
Mar 21, 2016, 18:13 UTC
Message-ID
<CAFZEwPO-cw2LOBh50uRbjRe-44XVC59Www=qygx5ABQG8f4N-A@mail.gmail.com>
In-Reply-To
<CAP8UFD1_mxej3YE_vU7DaXEsDpu-VA1YZtG5zkhLE2NXHpfL+Q@mail.gmail.com>

On Mon, Mar 21, 2016 at 11:23 PM, Christian Couder <christian.couder@gmail.com> wrote:

Show 32 quoted lines
> Hi Pranit,
>
> On Mon, Mar 21, 2016 at 8:29 AM, Pranit Bauva <pranit.bauva@gmail.com> wrote:
>> On Mon, Mar 21, 2016 at 12:48 PM, Johannes Schindelin
>> <Johannes.Schindelin@gmx.de> wrote:
>>> Hi Pranit,
>>>
>>> On Sun, 20 Mar 2016, Pranit Bauva wrote:
>>>
>>>> I could first move individual functions to bisect--helper.c.
>>>
>>> My suggestion would be to give it a try already with some functionality
>>> you deem small enough to move to the bisect--helper within a day or so. It
>>> is always good to test the waters like that, and to include this early
>>> work in the proposal, also to assess (and to let the reviewers assess) how
>>> feasible the project is.
>>
>> Sure! I will start with check_term_format().
>>
>> Also, I think implementing a new algorithm for bisect along with this
>> would be too big for a GSoC project
>
> Yeah, I also think so.
>
>> and I am no algorithm expert. I
>> will stick to --first-parent along with incremental rewrite.
>
> My opinion is that an incremental rewrite by itself is big enough for
> a GSoC. And it might be difficult to do something else that is bisect
> related at the same time. So if you want to do the rewrite, just focus
> on it. If you ever have some time left we will easily find other
> interesting bisect related improvements.

I just realised it after I finished rewriting a simple function. I will send that patch. It would be much better on doing one thing properly.

> If you really want to do "--first-parent" then you should probably add
> "Improve git bisect terms" to it in your proposal.
Previous: Christian Couder
Message 16 of 16 in “GSoC Project | Improvise git bisect”
  1. Pranit BauvaMar 19, 2016
  2. Matthieu MoyMar 19, 2016
  3. Christian CouderMar 19, 2016
  4. Pranit BauvaMar 19, 2016
  5. Stefan BellerMar 19, 2016
  6. Pranit BauvaMar 20, 2016
  7. Pranit BauvaMar 20, 2016
  8. Matthieu MoyMar 20, 2016
  9. Christian CouderMar 20, 2016
  10. Johannes SchindelinMar 20, 2016
  11. Pranit BauvaMar 20, 2016
  12. Matthieu MoyMar 20, 2016
  13. Johannes SchindelinMar 21, 2016
  14. Pranit BauvaMar 21, 2016
  15. Christian CouderMar 21, 2016
  16. Pranit BauvaMar 21, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.