git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sam Vilain <sam@vilain.net>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org, Joshua Roys <roysjosh@gmail.com>
Subject: Re: [GSoC] What is status of Git's Google Summer of Code 2008 projects?
Date: Mon, 21 Jul 2008 12:55:39 +1200	[thread overview]
Message-ID: <1216601739.6523.48.camel@maia.lan> (raw)
In-Reply-To: <200807210029.31543.jnareb@gmail.com>

On Mon, 2008-07-21 at 00:29 +0200, Jakub Narebski wrote:
> 1. GitTorrent
>  
> Student: Joshua Roys
> Mentor: Sam Vilain
> 
> I never got more response than "it is going slower than I would like, 
> [...] Other than that, it's going well, I think." from Joshua Roys.

> Mailing list archives for gittorrent mailing list doesn't show anything 
> interesting, either (last post is from 2007).
>   http://lists.utsl.gen.nz/pipermail/gittorrent/

That's a valid complaint.  I've posted a summary of the project status
there, and will keep as much related discussion as appropriate on-list
from here.

> Besides canonical repository gitweb
>   http://utsl.gen.nz/gitweb/?p=VCS-Git-Torrent
> there is also mirror at
>   http://repo.or.cz/w/VCS-Git-Torrent.git
> 
> There is some activity there... but no summary of it anywhere I could 
> find.

git-log | git-shortlog?  ;)

Sam.

  parent reply	other threads:[~2008-07-21  0:57 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-08  0:27 [GSoC] What is status of Git's Google Summer of Code 2008 projects? Jakub Narebski
2008-07-08  0:43 ` David Symonds
2008-07-08  1:00 ` Stephan Beyer
2008-07-08  1:14   ` Junio C Hamano
2008-07-08  1:47     ` Stephan Beyer
2008-07-08  7:39       ` Jakub Narebski
2008-07-08 14:42         ` Stephan Beyer
2008-07-08 16:12           ` Jakub Narebski
2008-07-08 16:34             ` Stephan Beyer
2008-07-08 17:31               ` Jakub Narebski
2008-07-08  4:08 ` Lea Wiemann
2008-07-08  7:20   ` J.H.
2008-07-08  4:19 ` Shawn O. Pearce
2008-07-08 16:31 ` Joshua Roys
2008-07-08 16:45   ` Johannes Schindelin
2008-07-08 17:22     ` Jakub Narebski
2008-07-08 17:00   ` Petr Baudis
2008-07-08 21:24 ` Sam Vilain
2008-07-09 10:18 ` Sverre Rabbelier
2008-07-09 10:56   ` Miklos Vajna
2008-07-09 11:36   ` Jakub Narebski
2008-07-20 22:29 ` Jakub Narebski
2008-07-20 22:43   ` Sverre Rabbelier
2008-07-20 22:57   ` Stephan Beyer
2008-07-21  0:55   ` Sam Vilain [this message]
2008-07-21  1:05     ` Johannes Schindelin
2008-07-21 10:23     ` Jakub Narebski
2008-07-21 10:40       ` Petr Baudis
2008-07-21 13:23         ` Joshua Roys
2008-07-21  3:22   ` Shawn O. Pearce
2008-08-17  5:26   ` Sverre Rabbelier
2008-08-14  2:57 ` Jakub Narebski
2008-08-14 12:42   ` Sam Vilain
2008-08-14 23:17     ` Petr Baudis
2008-08-14 23:23     ` Jakub Narebski
2008-08-14 23:04   ` Johannes Schindelin
2008-08-15 19:38   ` Lea Wiemann
2008-08-15 20:36     ` Jakub Narebski
2008-08-16  1:16       ` Stephan Beyer
2008-08-16  1:22         ` Shawn O. Pearce
2008-08-16  3:10         ` Jakub Narebski
2008-08-17 20:49   ` Marek Zawirski
2008-08-18  5:51     ` Shawn O. Pearce
2008-08-19  1:25   ` Joshua Roys
2008-08-20  6:19     ` Sam Vilain
2008-08-22 23:03   ` Stephan Beyer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1216601739.6523.48.camel@maia.lan \
    --to=sam@vilain.net \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    --cc=roysjosh@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).