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

Re: GSoC Project Selected | Incremental Rewrite of git bisect

From
Matthieu Moy <matthieu.moy@grenoble-inp.fr>
Date
Apr 25, 2016, 14:39 UTC
Message-ID
<vpqvb35sqge.fsf@anie.imag.fr>
In-Reply-To
<CAFZEwPMr=imv==kvVULy4PDYKW-0RRQ5a+X8DFqNFhNjCSyWKA@mail.gmail.com>
Pranit Bauva <pranit.bauva@gmail.com> writes:
>  - The more I dived in, the more it started to realize that my time
> line needs some restructuring which I guess can be determined by the
> above paragraphs.

Do not worry too much about the timeline. The timeline you attached to your project is not a plan to follow, but just a proof that you understood the amount of work to be done and that you have an idea on how to accomplish it.

I wouldn't be the first one to write "value [...] Responding to change over following a plan" ;-).

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/
Previous: Johannes SchindelinNext: Pranit Bauva
Message 3 of 18 in “GSoC Project Selected | Incremental Rewrite of git bisect”
  1. Pranit BauvaApr 23, 2016
  2. Johannes SchindelinApr 24, 2016
  3. Matthieu MoyApr 25, 2016
  4. [GSOC update] Week 1Pranit Bauva, May 8, 2016
  5. [GSOC Update] Week 2Pranit Bauva, May 15, 2016
  6. Matthieu MoyMay 15, 2016
  7. Junio C HamanoMay 15, 2016
  8. Junio C HamanoMay 15, 2016
  9. Pranit BauvaMay 15, 2016
  10. [GSoC Update] Week 3Pranit Bauva, May 22, 2016
  11. [GSOC Update] Week 2Pranit Bauva, May 30, 2016
  12. Pranit BauvaMay 30, 2016
  13. [GSOC Update] Week 5Pranit Bauva, Jun 6, 2016
  14. [GSOC Update] Week 6Pranit Bauva, Jun 13, 2016
  15. [GSOC Update] Week 7Pranit Bauva, Jun 20, 2016
  16. [GSOC Update] Week 8Pranit Bauva, Jun 27, 2016
  17. [GSOC Update] Week 9Pranit Bauva, Jul 3, 2016
  18. [GSOC Update] Week 10Pranit Bauva, Jul 12, 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.