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

Re: Histogram diff, libgit2 enhancement, libgit2 => git merge (GSOC)

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 20, 2011, 18:25 UTC
Message-ID
<7vhbaxwswo.fsf@alter.siamese.dyndns.org>
In-Reply-To
<op.vsm1yszq2m56ex@localhost.localdomain>
"Pavel Raiskup" <xraisk00@gmail.com> writes:
> I have one theoretical question -- what if the benchmarking/study of
> histogram diff leads to conclusion that this algorithm will not be
> useful for upstream?  Does it mean "fail" in terms of GSOC?

Not necessarily. A negative result is often as valuable as a positive result.

It will take a clearly good implementation to justify why a negative result is a success, though. If it is clear to the reviewers that the implementation is poorly done, the negative conclusion does not necessarily mean that use of the histogram algorithm is a bad approach---it would just mean the particular implementation that didn't implement it well was, and then the GSoC task may have to be marked as a failure. But otherwise, if the submission is done with the usual code quality we would expect from contributors and explained well in its log message (either positive or negative), I would say it should be considered a "success".

Previous: Pavel RaiskupNext: Vicent Marti
Message 4 of 13 in “Histogram diff, libgit2 enhancement, libgit2 => git merge (GSOC)”
  1. Pavel RaiskupMar 20, 2011
  2. Shawn PearceMar 20, 2011
  3. Pavel RaiskupMar 22, 2011
  4. Junio C HamanoMar 20, 2011
  5. Vicent MartiMar 20, 2011
  6. Jeff KingMar 20, 2011
  7. Vicent MartiMar 21, 2011
  8. Pavel RaiskupMar 22, 2011
  9. Jeff KingMar 22, 2011
  10. Junio C HamanoMar 22, 2011
  11. Jonathan NiederMar 21, 2011
  12. Pavel RaiskupMar 22, 2011
  13. Vincent van RavesteijnMar 23, 2011

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.