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

Re: [GSoC] What is status of Git's Google Summer of Code 2008 projects?

From
Jakub Narebski <jnareb@gmail.com>
Date
Aug 14, 2008, 23:23 UTC
Message-ID
<200808150123.33546.jnareb@gmail.com>
In-Reply-To
<1218717743.11530.99.camel@maia.lan>
On Thu, 14 Aug 2008, Sam Vilain wrote:
Show 11 quoted lines
> On Thu, 2008-08-14 at 04:57 +0200, Jakub Narebski wrote:
>>
>> 1. GitTorrent
>>  
>> Student: Joshua Roys
>> Mentor: Sam Vilain
>> 
>> If I remember correctly at midterm it was deemed to be somewhat late;
>> metainfo was done, tracker was in works, some core infrastructure
>> and beginnings of peer to peer:
>>   http://thread.gmane.org/gmane.comp.version-control.git.gittorrent/1
[...]
Show 12 quoted lines
>> Status: I have no idea how close GitTorrent is to completion (where by 
>> completion I mean ready, tested and benchmarked code running e.g. on 
>> kernel.org).  I'm not sure if it is meant to be incorporated in git, 
>> even in contrib, or remain separate like StGIT, TopGit or jgit.
> 
> The scope outlined in the GitTorrent proposal was a little bit more of a
> research project; being ready for production use on kernel.org or having
> code ready to merge to git was not directly a deliverable.
> 
> The approved idea at the outset of *this* project was to try out the RFC
> protocol design as it stands, iron out the weaknesses and see how it
> performs. [...]

That is a very good idea, but neither http://git.or.cz/gitwiki/SoC2008Projects#GitTorrent nor http://code.google.com/soc/2008/git/appinfo.html?csaid=F544F0DAA82AFDFC tells me that it is more about prototype implementation, or even pre-prototype implementation (testing protocol design), than actually implementing it in the state for it to be ready to use.

What I (and I guess also GSoC 2008 admins) would know is how far this research on GitTorrent Protocol went; what milestones were achieved and what were missed...

-- 
Jakub Narebski
Poland
Previous: Petr BaudisNext: Johannes Schindelin
Message 35 of 46 in “[GSoC] What is status of Git's Google Summer of Code 2008 projects?”
  1. Jakub NarebskiJul 8, 2008
  2. David SymondsJul 8, 2008
  3. Stephan BeyerJul 8, 2008
  4. Junio C HamanoJul 8, 2008
  5. Stephan BeyerJul 8, 2008
  6. Jakub NarebskiJul 8, 2008
  7. Stephan BeyerJul 8, 2008
  8. Jakub NarebskiJul 8, 2008
  9. Stephan BeyerJul 8, 2008
  10. Jakub NarebskiJul 8, 2008
  11. Lea WiemannJul 8, 2008
  12. J.H.Jul 8, 2008
  13. Shawn O. PearceJul 8, 2008
  14. Joshua RoysJul 8, 2008
  15. Johannes SchindelinJul 8, 2008
  16. Jakub NarebskiJul 8, 2008
  17. Petr BaudisJul 8, 2008
  18. Sam VilainJul 8, 2008
  19. Sverre RabbelierJul 9, 2008
  20. Miklos VajnaJul 9, 2008
  21. Jakub NarebskiJul 9, 2008
  22. Jakub NarebskiJul 20, 2008
  23. Sverre RabbelierJul 20, 2008
  24. Stephan BeyerJul 20, 2008
  25. Sam VilainJul 21, 2008
  26. Johannes SchindelinJul 21, 2008
  27. Jakub NarebskiJul 21, 2008
  28. Petr BaudisJul 21, 2008
  29. Joshua RoysJul 21, 2008
  30. Shawn O. PearceJul 21, 2008
  31. Sverre RabbelierAug 17, 2008
  32. Jakub NarebskiAug 14, 2008
  33. Sam VilainAug 14, 2008
  34. Petr BaudisAug 14, 2008
  35. Jakub NarebskiAug 14, 2008
  36. Johannes SchindelinAug 14, 2008
  37. Lea WiemannAug 15, 2008
  38. Jakub NarebskiAug 15, 2008
  39. Stephan BeyerAug 16, 2008
  40. Shawn O. PearceAug 16, 2008
  41. Jakub NarebskiAug 16, 2008
  42. Marek ZawirskiAug 17, 2008
  43. Shawn O. PearceAug 18, 2008
  44. Joshua RoysAug 19, 2008
  45. Sam VilainAug 20, 2008
  46. Stephan BeyerAug 22, 2008

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.