git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Chiyuan Zhang" <pluskid@gmail.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: git@vger.kernel.org
Subject: Re: [GSoC2008]What's wrong with last years Gittorrent?
Date: Mon, 24 Mar 2008 15:34:32 +0800	[thread overview]
Message-ID: <b6f0e9dd0803240034v4b53cc3fo9bc890fb3f60b919@mail.gmail.com> (raw)
In-Reply-To: <20080324072434.GN8410@spearce.org>

OK! Thanks for this information. I think I should double
check that I'm legal to work on this before trying to
apply this. :p

2008/3/24, Shawn O. Pearce <spearce@spearce.org>:
> Chiyuan Zhang <pluskid@gmail.com> wrote:
>  > I'm planning to apply Google Summer of Code this year. I noticed
>  > on the git project page there's a gittorrent implementation. I'm
>  > interested in this. But later I found there was also a similar
>  > project (accepted) in last year's SoC: GitTorrent Server and Peer,
>  > written in Python. Unfortunately, the two links on that page aren't
>  > available any more. So I'm wondering what's the status of last
>  > year's GitTorrent? Is there something wrong with that? If any, what
>  > caused the problem and what's the differences between this year's
>  > and that one?
>
>
> Last year's GitTorrent implementation never got off the ground.
>  The student who we accepted was unable to actually participate due
>  to legal problems, and we did not find out about it until too late
>  in the program to select a replacement student.
>
>  So in short, there's nothing wrong with last year's GitTorrent,
>  as there was no last year's GitTorrent.  Hence it is on the list
>  again for this year.  :)
>
>  --
>
> Shawn.
>

      reply	other threads:[~2008-03-24  7:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-24  1:14 [GSoC2008]What's wrong with last years Gittorrent? Chiyuan Zhang
2008-03-24  7:24 ` Shawn O. Pearce
2008-03-24  7:34   ` Chiyuan Zhang [this message]

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=b6f0e9dd0803240034v4b53cc3fo9bc890fb3f60b919@mail.gmail.com \
    --to=pluskid@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=spearce@spearce.org \
    /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).