git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Sverre Rabbelier" <alturin@gmail.com>
To: "Jakub Narebski" <jnareb@gmail.com>
Cc: git@vger.kernel.org, "Sam Vilain" <sam@vilain.net>,
	"Joshua Roys" <roysjosh@gmail.com>,
	"David Symonds" <dsymonds@gmail.com>,
	"Lea Wiemann" <LeWiemann@gmail.com>,
	"John Hawley" <warthog19@eaglescrag.net>,
	"Marek Zawirski" <marek.zawirski@gmail.com>,
	"Shawn O. Pearce" <spearce@spearce.org>,
	"Miklos Vajna" <vmiklos@frugalware.org>,
	"Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
	"Stephan Beyer" <s-beyer@gmx.net>,
	"Christian Couder" <chriscool@tuxfamily.org>,
	"Daniel Barkalow" <barkalow@iabervon.org>,
	"Junio Hamano" <gitster@pobox.com>
Subject: Re: [GSoC] Git projects for Google Summer of Code 2008 final evaluation
Date: Fri, 5 Sep 2008 00:44:59 +0200	[thread overview]
Message-ID: <bd6139dc0809041544o427356c9i40a28b1c182817eb@mail.gmail.com> (raw)
In-Reply-To: <200809042315.58898.jnareb@gmail.com>

Heya,

Replying to:
> 2. git-statistics
>
> Student: Sverre Rabbelier
> Mentor: David Symonds

On Thu, Sep 4, 2008 at 23:15, Jakub Narebski <jnareb@gmail.com> wrote:
> So students and mentors, please write what do you think current status
> of project is: is it done, is it ready, is it perhaps already merged
> in, or can be merged in at any time.  Please write also what wasn't
> done, or what should be done different way (hindsight and all that).

I consider it a successfull project, although it might not be what
some hoped it would be, I am happy with it. I plan to submit it for
inclusion in /contrib in the near future. I hope to work on improving
move detection in git log when time allows.

> Students, could you please tell us if you plan to work on git further,
> and in what range (how much time can you get to work on git). What do
> you think about git development community? What have you learned from
> participating in GSoC?

I very much plan to continue development, now that my day-to-day life
seems to have stabilized (after being on vacaction to the USA for a
month). I enjoyed working with the git community, especially the 'real
time' help on #git has been very usefull!

-- 
Cheers,

Sverre Rabbelier

  parent reply	other threads:[~2008-09-04 22:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-04 21:15 [GSoC] Git projects for Google Summer of Code 2008 final evaluation Jakub Narebski
2008-09-04 22:10 ` Daniel Barkalow
2008-09-04 22:22 ` Joshua Roys
2008-09-04 22:36 ` Stephan Beyer
2008-09-04 22:44 ` Sverre Rabbelier [this message]
2008-09-04 22:55 ` Miklos Vajna
2008-09-04 23:04 ` Shawn O. Pearce
2008-09-08 17:46 ` Marek Zawirski
2008-09-09 14:52 ` Johannes Schindelin
2008-09-15 12:13 ` Jakub Narebski
2008-09-15 12:40   ` Johannes Schindelin
2008-09-15 14:08     ` Shawn O. Pearce

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=bd6139dc0809041544o427356c9i40a28b1c182817eb@mail.gmail.com \
    --to=alturin@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=LeWiemann@gmail.com \
    --cc=barkalow@iabervon.org \
    --cc=chriscool@tuxfamily.org \
    --cc=dsymonds@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jnareb@gmail.com \
    --cc=marek.zawirski@gmail.com \
    --cc=roysjosh@gmail.com \
    --cc=s-beyer@gmx.net \
    --cc=sam@vilain.net \
    --cc=spearce@spearce.org \
    --cc=sverre@rabbelier.nl \
    --cc=vmiklos@frugalware.org \
    --cc=warthog19@eaglescrag.net \
    /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).