Re: Re: [RFH] GSoC 2015 application
- From
Matthieu Moy <matthieu.moy@grenoble-inp.fr>
- Date
- Feb 24, 2015, 23:56 UTC
- Message-ID
- <vpqh9uavp6q.fsf@anie.imag.fr>
- In-Reply-To
- <c9ff859363d2d637b3607aaf6cb9295d@www.dscho.org>
Johannes Schindelin <johannes.schindelin@gmx.de> writes:
Show 19 quoted lines
> Hi Junio, > > On 2015-02-24 19:25, Junio C Hamano wrote: >> On Tue, Feb 24, 2015 at 9:32 AM, Matthieu Moy >> <Matthieu.Moy@grenoble-inp.fr> wrote: >>> About the proposal: >>> >>> The idea of this project is to dive into the Git source code and >>> convert, say, git-add--interactive.perl and/or git stash into proper C >>> code, making it a so-called "built-in". >>> >>> My advice would be to try converting several small scripts, and avoid >>> targetting a big one.... >>> add--interactive and stash are relatively complex beasts, perhaps >>> git-pull.sh would be easier to start with. >> >> Yeah, I think that is a very good suggestion. > > Well, git-pull.sh is really small. I did not want to give the impression that the Git project is giving out freebies. But I have no objection to change it if you open that PR.
To get an idea, I counted the lines of code written by the student I mentored last year:
$ git log --author tanayabh@gmail.com -p | diffstat -s 43 files changed, 1225 insertions(+), 367 deletions(-)
I would consider this GSoC as "average" (i.e. not exceptionnally good, but certainly not a bad one either), so you may hope for more, but you should not _expect_ much more IMHO.
In comparison:
$ wc -l git-add--interactive.perl 1654 git-add--interactive.perl $ wc -l git-stash.sh 617 git-stash.sh
I'd expect a rewrite in C to at least double the number of lines of code, so rewriting git-stash would mean writting at least as many lines of code as the GSoC above. git-add--interactive.perl would be rather far above.
But my point was not to convert _only_ git-pull.sh, but to have a GSoC starting with this one and plan more. Then, depending on how it goes, you can adjust the target.
This all depends on what you intend to do if the student does not finish the job. If you're going to do the rewrite yourself anyway, then having the student do even half of it is good already. If you're not going to finish the job by yourself, then a 95%-done-rewrite means a piece of code posted on the mailing list and never merged (and a lot of time wasted).
In any case, these are just advices, certainly not objections or hard requests to change.
-- Matthieu Moy http://www-verimag.imag.fr/~moy/ -- -- *** Please reply-to-all at all times *** *** (do not pretend to know who is subscribed and who is not) *** *** Please avoid top-posting. *** The msysGit Wiki is here: https://github.com/msysgit/msysgit/wiki - Github accounts are free. You received this message because you are subscribed to the Google Groups "msysGit" group. To post to this group, send email to msysgit@googlegroups.com To unsubscribe from this group, send email to msysgit+unsubscribe@googlegroups.com For more options, and view previous threads, visit this group at http://groups.google.com/group/msysgit?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups "Git for Windows" group. To unsubscribe from this group and stop receiving emails from it, send an email to msysgit+unsubscribe@googlegroups.com. For more options, visit https://groups.google.com/d/optout.