Re: Re: Re: GSoC Project | Convert interactive rebase to C

[Johannes Schindelin <Johannes.Schindelin@gmx.de>]

Hi Ivan,

On Sat, 25 Mar 2017, Inaw Tham wrote:

> Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> > On Tue, 21 Mar 2017, Ivan Tham wrote:
> > > Stefan Beller <sbeller@google.com> wrote:
> > > > On Mon, Mar 20, 2017 at 9:41 AM, Ivan Tham <pickfire@riseup.net> wrote:
> > > >
> > > > > I am interested to work on "Convert interactive rebase to C"
> > > >
> > > > +cc Johannes, who recently worked on rebase and the sequencer.
> > 
> > Glad you are interested! Please note that large parts of the
> > interactive rebase are already in C now, but there is enough work left
> > in that corner.
> 
> Glad to hear that, I would really like to see interactive rebase in C.

Please note that a notable part already made it into C in v2.12.1. There
are still a few loose ends to tie, of course; it still makes for a great
head start on your project, methinks.

> > > > > aiming to port most builtins stuff to C in which we can reduce
> > > > > the size of git. Additionally, I would also like to convert
> > > > > scripts to builtins as an additional milestone.
> > 
> > Careful. It is a ton of work to get the rebase -i conversion done, and
> > then a ton of work to get it integrated. That will fill 3 months, very
> > easily.
> 
> My main aim is to reduce the extra dependency of perl, but planning to
> start with rebase, can I make that an optional task where I can help out
> after I had completed my main task during gsoc?

Sure, you can make it an optional task, and I would be very happy if you
followed up on it even after GSoC!

As far as the Perl dependency is concerned, I actually think there is only
one serious one left: git add -i.

Granted, there is send-email, but it really does not matter all that much
these days *except* if you want to use Git to contribute to projects that
still use a mailing list-based patch submission process (the ones that
come to mind are: Git, Linux and Cygwin). Most Git users actually do not
submit any patches to mailing lists, therefore I tend to ignore this one.

The rest of the Perl scripts interacts with foreign SCMs (archimport,
cvsexportcommit, cvsimport, cvsserver, and svn). I *guess* that it would
be nice to follow up on the remote-svn work (which has not really gone
anywhere so far, AFAICT the main driving contributor pursues different
projects these days), but IMHO none of these are really needed to run Git.

Ciao,
Johannes