From: Jakub Narebski <jnareb@gmail.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: git@vger.kernel.org
Subject: Re: Google Summer of Code 2009
Date: Sat, 10 Jan 2009 11:33:04 -0800 (PST) [thread overview]
Message-ID: <m3privyn20.fsf@localhost.localdomain> (raw)
In-Reply-To: <20090107183033.GB10790@spearce.org>
"Shawn O. Pearce" <spearce@spearce.org> writes:
> The application answers really need to be reworked; we need to
> address our 2008 results in these parts.
By the way, do you know what happened with git-sequencer project?
If I remember correctly there was agreement on sequences mini-language
(I think), and there was git-sequencer prototype in shell, using
git-cherry-pick if I remember correctly, and even git-rebase and
git-am etc reworked to make use of git-sequencer. Stephan Beyer wrote
that he has some preliminary version of builtin git-sequencer (in C),
and that it makes git-rebase--interactive and like faster than current
implementation... but builtin sequencer never materialized on git
mailing list as a patch, if I remember correctly, and of course it was
not merged into git either.
> The ideas box is once again open for suggestions. Please start
> proposing student projects, and possible mentors.
Hmm... take a look what features competition has (Darcs, Bazaar-NG,
Subversion, Mercurial, Monotone)...
>
>
> Since the program is smaller, there is a chance we won't be accepted
> this year due to space constraints. But I think its still worthwhile
> to prepare everything and hope for the best. And before you can
> ask, no, my employee status with OSPO doesn't improve our odds
> for acceptance. :-)
Perhaps at least _one_ project. I think that resumable clone /
resumable fetch would be a good thing to have...
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2009-01-10 19:35 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-07 18:30 Google Summer of Code 2009 Shawn O. Pearce
2009-01-07 23:11 ` Miklos Vajna
2009-01-07 23:12 ` Alex Riesen
2009-01-07 23:14 ` Shawn O. Pearce
2009-01-07 23:30 ` Johannes Schindelin
2009-01-07 23:40 ` Alex Riesen
2009-01-08 7:55 ` Sam Vilain
2009-01-10 19:33 ` Jakub Narebski [this message]
2009-01-10 19:58 ` Johannes Schindelin
2009-01-12 13:01 ` Christian Couder
2009-01-14 22:01 ` Stephan Beyer
2009-01-12 11:16 ` Andreas Ericsson
2009-01-12 13:20 ` Christian Couder
2009-01-12 15:35 ` Shawn O. Pearce
2009-01-12 13:25 ` Johannes Schindelin
2009-01-12 15:33 ` Shawn O. Pearce
2009-01-12 17:23 ` Johannes Schindelin
2009-01-12 17:48 ` Shawn O. Pearce
2009-01-12 15:37 ` Shawn O. Pearce
-- strict thread matches above, loose matches on Subject: below --
2009-03-21 9:41 Yoshinori K. Okuji
2009-03-21 16:26 ` Bean
2009-03-21 19:54 ` Vesa Jääskeläinen
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=m3privyn20.fsf@localhost.localdomain \
--to=jnareb@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.