From: Stephan Beyer <s-beyer@gmx.net>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org, Sam Vilain <sam@vilain.net>,
Joshua Roys <roysjosh@gmail.com>,
Sverre Rabbelier <alturin@gmail.com>,
Sverre Rabbelier <sverre@rabbelier.nl>,
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>,
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:36:53 +0200 [thread overview]
Message-ID: <20080904223653.GA15170@leksak.fem-net> (raw)
In-Reply-To: <200809042315.58898.jnareb@gmail.com>
Hi,
my reply belongs to:
> 6. git-sequencer
>
> Student: Stephan Beyer
> Mentor: Christian Couder, Daniel Barkalow
Jakub Narebski 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.
It is done, but not ready.
This means, we, my mentors and I, are currently still reviewing the code.
But I am pinched for time until the end of September due to an important
exam. My mentors also have not much time and so everything is a little
slowed down.
When they ACK, it will be sent to the list.
> Please write also what wasn't done, or what should be done different
> way (hindsight and all that).
During the GSoC application phase I have done a breakdown and I declared
two items as "bonus" if I am really quick with the rest. But I wasn't
that quick, so none of the bonus items have even begun.
Those were:
6. [bonus] rewrite the users in C
7. [bonus] discuss (with git development team and/or mentor)
sequencer features needed for gitk and implement them
Now I think (7) is even more needed/interesting, e.g. to be able to do
interactive rebasing with gitk.
And (6) shouldn't be that hard, but it will be even more interesting when
sequencer is libified. I have some ideas for that, but I think, this is
not so important in near time. Perhaps, there are other parts that need
some libification first. :)
> Students, could you please tell us if you plan to work on git further,
Yes!
But due to my current lack of time I have ignored some topics on the
list that I am interested in. :-(
> and in what range (how much time can you get to work on git).
This is fluctating.
> What do you think about git development community?
Strange people. Lunatics. Geeks.
:-)
> What have you learned from participating in GSoC?
In the beginning: portable shell is a mess. ;)
Well, I guess I have learned a lot more...
Regards,
Stephan
--
Stephan Beyer <s-beyer@gmx.net>, PGP 0x6EDDD207FCC5040F
next prev parent reply other threads:[~2008-09-04 22:38 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 [this message]
2008-09-04 22:44 ` Sverre Rabbelier
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=20080904223653.GA15170@leksak.fem-net \
--to=s-beyer@gmx.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=LeWiemann@gmail.com \
--cc=alturin@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=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).