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
Stephan Beyer <s-beyer@gmx.net>
Date
Aug 22, 2008, 23:03 UTC
Message-ID
<20080822230339.GA14684@leksak.fem-net>
In-Reply-To
<200808140457.56464.jnareb@gmail.com>
Hi,
Jakub Narebski wrote:
> 6. git-sequencer
> 
> Student: Stephan Beyer

The Google Open Source blog had an article about this thread[1] and I noted that I forgot to inform you about my project here.

 1. http://google-opensource.blogspot.com/2008/08/git-and-google-summer-of-code.html

Until Sunday, Aug 17, I have been on testing, code cleanup and bugfixing of the builtin-sequencer. Then I've sent this version of the patchset to my mentors for a final review before the real hard one (on the list *g*) and then I went away for three days. That's perhaps why I forgot about this thread :)

That's also why there's not yet a patchset on the list.

I know there are a few people that already use (or at least used) the (builtin) sequencer. For the other curious people: the branches "seq-builtin-dev" (development branch) or "seq-builtin-rfc" (rebased patchset) on repo.or.cz[2] can be used, because I currently do not know how long it will take until I send it to the list but I hope it will be soon.

 2. http://repo.or.cz/w/git/sbeyer.git (seq-builtin-rfc, seq-builtin-dev)

(The last commit in seq-builtin-rfc is a test and I don't really like it atm. It's reverted in the -dev branch.)

What else to say? I will have not *much* time for git each day until the end of September because of some other work and, especially, an important exam. But I also try to take some time for git. I also intend to keep contributing (at least small stuff) after the builtin sequencer got into git. (I expect this is still some hard work until the last one who has doubts is somehow satisfied.)

Kind regards,
  Stephan
-- 
Stephan Beyer <s-beyer@gmx.net>, PGP 0x6EDDD207FCC5040F
Previous: Sam Vilain
Message 46 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.