git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: What's cooking in git.git (Aug 2018, #05; Mon, 20)

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Aug 22, 2018, 21:44 UTC
Message-ID
<nycvar.QRO.7.76.6.1808222339490.73@tvgsbejvaqbjf.bet>
In-Reply-To
<xmqqo9dumh9z.fsf@gitster-ct.c.googlers.com>
Hi Junio,
On Wed, 22 Aug 2018, Junio C Hamano wrote:
Show 20 quoted lines
> Junio C Hamano <gitster@pobox.com> writes:
> 
> > Here are the topics that have been cooking.  Commits prefixed with
> > '-' are only in 'pu' (proposed updates) while commits prefixed with
> > '+' are in 'next'.  The ones marked with '.' do not appear in any of
> > the integration branches, but I am still holding onto them.
> 
> Mentors (and GSoC students),
> 
> Two topics your students have worked on conflict heavily at the
> philosophical level; "rebase in C" rewrite assumes that backend
> implementations are forever written in shell and can be invoked by
> dot-sourcing ". git-rebase--$backend", while violating that
> assumption is the whole point of "rebase-i in C" rewrite.  Trying to
> use them together would of course not work without a bit of "last
> mile" further glue.
> 
> I do not think neither topic is ready for the upcoming release, but
> can you help your students to come up with "the final step" to make
> the fruits of their effort work well together?

Pratik is unfortunately unable to spare time, as the university schedule in Nepal does not really have such a thing as summer break. He made a heroic effort to work on GSoC nevertheless, and I am quite proud of how much he learned, and that he managed to finish the patches (with my help).

As I have a vested interest in a substantially faster `git rebase` on Windows, I will take care of the `rebase-in-c*` patches.

FWIW I am a lot more bold about these builtins, and want to get them into Git for Windows v2.19.0, either as full replacements, or like I did with the difftool: by offering them as experimental options in the installer.

Maybe this will remain a dream, but maybe, just maybe, I will manage to do this, with your help.

Ciao, Dscho

Previous: Junio C HamanoNext: Junio C Hamano
Message 3 of 6 in “What's cooking in git.git (Aug 2018, #05; Mon, 20)”
  1. Junio C HamanoAug 20, 2018
  2. Junio C HamanoAug 22, 2018
  3. Johannes SchindelinAug 22, 2018
  4. Junio C HamanoAug 22, 2018
  5. Johannes SchindelinAug 23, 2018
  6. ag/rebase-i-in-c, was Re: What's cooking in git.git (Aug 2018, #05; Mon, 20)Alban Gruin, Aug 24, 2018

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.