From: Robert David <robert.david.public@gmail.com>
To: Thomas Rast <trast@student.ethz.ch>
Cc: Jeff King <peff@peff.net>, Jonathan Nieder <jrnieder@gmail.com>,
Git Mailing List <git@vger.kernel.org>,
Matthieu Moy <Matthieu.Moy@imag.fr>
Subject: Re: GSOC idea: build in scripts and cleanups
Date: Wed, 30 Mar 2011 23:17:17 +0200 [thread overview]
Message-ID: <201103302317.17855.robert.david.public@gmail.com> (raw)
In-Reply-To: <201103301739.12691.trast@student.ethz.ch>
[-- Attachment #1: Type: Text/Plain, Size: 1483 bytes --]
Dne středa 30 března 2011 17:39:12 Thomas Rast napsal(a):
> Jeff King wrote:
> > On Mon, Mar 28, 2011 at 10:55:22AM +0200, Robert David wrote:
> > > > As far as cleanup versus features, I think Thomas would have to
> > > > comment on that. He is the one who did the most work on patch-mode,
> > > > and therefore the one who most thinks it needs cleaned up. :)
> > >
> > > Is Thomas going to be a mentor in this task?
> >
> > I hope so. I can also co-mentor if it helps.
>
> I'm certainly ready; I didn't propose any projects that I would not
> also mentor. (However, I won't mentor more than one...)
Thank you for your attention.
>
> Note that while it's certainly a bonus, porting it to C probably makes
> the project more difficult and time-consuming. We'll have to see in
> the proposal timelines however.
It is not a big problem to me. I plan to begin full time work on this in half
June.
Before that I plan some cleanups and fixes to simplify the upcoming porting.
>
> As for cleanup, my gut feeling right now is that the Perl code can
> probably cope with incremental cleanups as required for each feature.
> On the other hand, the C port should start from a clean redesign so as
> to not rewrite it twice.
I agree that porting to C should be done from scratch. Thats why I would clean
and extend the script first to make a "preview". Than when it will comply
with requirements, I will port that from scratch to C.
Robert
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 230 bytes --]
next prev parent reply other threads:[~2011-03-30 21:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-26 0:41 GSOC idea: build in scripts and cleanups Robert David
2011-03-26 2:14 ` Jonathan Nieder
2011-03-26 13:39 ` Jeff King
2011-03-28 8:55 ` Robert David
2011-03-28 14:21 ` Jeff King
2011-03-30 15:39 ` Thomas Rast
2011-03-30 21:17 ` Robert David [this message]
2011-04-03 21:17 ` Robert David
2011-04-04 7:43 ` Robert David
2011-04-04 18:09 ` Junio C Hamano
2011-04-04 18:51 ` Robert David
2011-04-05 17:07 ` Jeff King
2011-04-05 18:18 ` Junio C Hamano
2011-04-05 16:52 ` Jeff King
2011-04-05 23:27 ` Robert David
2011-04-07 13:30 ` Robert David
2011-04-07 22:19 ` Junio C Hamano
2011-04-08 9:51 ` Robert David
2011-04-11 6:34 ` Jonathan Nieder
2011-04-17 18:50 ` Robert David
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201103302317.17855.robert.david.public@gmail.com \
--to=robert.david.public@gmail.com \
--cc=Matthieu.Moy@imag.fr \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=peff@peff.net \
--cc=trast@student.ethz.ch \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).