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
Junio C Hamano <gitster@pobox.com>
Date
Aug 22, 2018, 17:40 UTC
Message-ID
<xmqqo9dumh9z.fsf@gitster-ct.c.googlers.com>
In-Reply-To
<xmqqsh38admf.fsf@gitster-ct.c.googlers.com>
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?

Thanks.
Previous: Junio C HamanoNext: Johannes Schindelin
Message 2 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.