From: Jonathan Nieder <jrnieder@gmail.com>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Avery Pennarun <apenwarr@gmail.com>,
Sverre Rabbelier <srabbelier@gmail.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: native-git-svn: A Summer of Code 2010 proposal
Date: Sat, 20 Mar 2010 16:04:07 -0500 [thread overview]
Message-ID: <20100320210406.GA29899@progeny.tock> (raw)
In-Reply-To: <f3271551003201334o4919cd47s44d06288b0d6068b@mail.gmail.com>
Hi,
Ramkumar Ramachandra wrote:
> I just prepared another revision of my proposal- I've tried to be
> clearer about the objective, and included a timeline this time.
Very nice. Thanks!
> == Timeline ==
The one thing I worry about is that you are proposing to wait a while
before submitting your changes upstream. I would suggest pushing
whatever pieces work to contrib/ early on to get more feedback from
reviewers and testers. (I am saying this selfishly, as a potential
tester.)
> July 10 - July 16: Scrub code and write documentation for mid-term
> evaluations. Commit changes to the remote helper to upstream. Try to
> get the other changes into `next`.
In particular, this seems like very little time to get the code into
shape for git.git.
Hope that helps.
Cheers,
Jonathan
next prev parent reply other threads:[~2010-03-20 21:03 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-19 17:18 native-git-svn: A Summer of Code 2010 proposal Ramkumar Ramachandra
2010-03-19 18:32 ` Avery Pennarun
2010-03-19 18:39 ` Sverre Rabbelier
2010-03-19 21:30 ` Avery Pennarun
2010-03-20 9:19 ` Ramkumar Ramachandra
2010-03-20 10:48 ` Johannes Schindelin
2010-03-20 20:34 ` Ramkumar Ramachandra
2010-03-20 20:55 ` Ramkumar Ramachandra
2010-03-20 21:04 ` Jonathan Nieder [this message]
2010-03-21 10:26 ` Johannes Schindelin
2010-03-21 11:08 ` Jonathan Nieder
2010-03-21 11:47 ` Johannes Schindelin
2010-03-21 12:25 ` Ramkumar Ramachandra
2010-03-21 12:31 ` Johannes Schindelin
2010-03-21 12:36 ` Sverre Rabbelier
2010-03-21 17:58 ` Jonathan Nieder
2010-03-22 0:33 ` Daniel Barkalow
2010-03-22 2:41 ` Christian Couder
2010-03-22 3:49 ` Ramkumar Ramachandra
2010-03-22 11:33 ` Johannes Schindelin
[not found] ` <f3271551003220643j3a726d09o2d3a078292fd8bf6@mail.gmail.com>
2010-03-22 19:52 ` Johannes Schindelin
2010-03-23 7:49 ` Ramkumar Ramachandra
2010-03-21 16:43 ` Best example of GSoC student participation (was: Re: native-git-svn: A Summer of Code 2010 proposal) Jakub Narebski
2010-03-21 17:27 ` Best example of GSoC student participation Johannes Schindelin
2010-03-20 21:58 ` native-git-svn: A Summer of Code 2010 proposal Daniel Barkalow
2010-03-20 22:19 ` Ramkumar Ramachandra
2010-03-21 5:36 ` Ramkumar Ramachandra
2010-03-21 22:56 ` Daniel Barkalow
2010-03-21 17:08 ` Ilari Liusvaara
2010-03-21 7:40 ` Peter Baumann
2010-03-21 23:51 ` Dave Olszewski
2010-03-19 20:53 ` Jonathan Nieder
2010-03-19 21:00 ` Johannes Schindelin
-- strict thread matches above, loose matches on Subject: below --
2010-03-27 5:40 Steven Michalske
2010-03-27 6:46 ` Ramkumar Ramachandra
2010-03-27 8:03 ` Steven Michalske
2010-03-27 9:19 ` Eric Raymond
[not found] ` <f3271551003280225v17af30d4s6d3d24b4d548ff7d@mail.gmail.com>
2010-03-28 12:10 ` Eric Raymond
2010-03-29 20:04 ` Ramkumar Ramachandra
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=20100320210406.GA29899@progeny.tock \
--to=jrnieder@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=apenwarr@gmail.com \
--cc=artagnon@gmail.com \
--cc=git@vger.kernel.org \
--cc=srabbelier@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 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.