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

Re: [PATCH v5 1/8] technical doc: add a design doc for the evolve command

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 15, 2019, 18:23 UTC
Message-ID
<xmqqlg2g6hcv.fsf@gitster-ct.c.googlers.com>
In-Reply-To
<20190215043105.163688-1-sxenos@google.com>
sxenos@google.com writes:
Show 8 quoted lines
> From: Stefan Xenos <sxenos@google.com>
>
> This document describes what a change graph for
> git would look like, the behavior of the evolve command,
> and the changes planned for other commands.
>
> Signed-off-by: Stefan Xenos <sxenos@google.com>
> ---

It would really need a summary of what changed since the earlier rounds, if a series this size wants to be re-read by those who helped the previous one.

I briefly looked at the patches (and the diff against the previous one that has been in 'pu') and saw a few comments that say "needs further work". What's the intention? Unfinished but soliciting further comments and sanity checks to help polishing the finished parts (if that is the case that is perfectly fine, but it would help those who want to help if you are clear about it)?

I'll read them through laster today or tomorrow with fresh set of eyes; thanks for working on this.

Previous: sxenos@google.comNext: Stefan Xenos
Message 9 of 11 in “technical doc: add a design doc for the evolve command”
  1. 1/8 technical doc: add a design doc for the evolve commandsxenos@google.com, Feb 15, 2019
  2. 2/8 sha1-array: implement oid_array_readonly_containssxenos@google.com, Feb 15, 2019
  3. 3/8 ref-filter: add the metas namespace to ref-filtersxenos@google.com, Feb 15, 2019
  4. 4/8 evolve: add support for parsing metacommitssxenos@google.com, Feb 15, 2019
  5. 5/8 evolve: add the change-table structuresxenos@google.com, Feb 15, 2019
  6. 6/8 evolve: add support for writing metacommitssxenos@google.com, Feb 15, 2019
  7. 7/8 evolve: implement the git change commandsxenos@google.com, Feb 15, 2019
  8. 8/8 evolve: add the git change list commandsxenos@google.com, Feb 15, 2019
  9. Junio C HamanoFeb 15, 2019
  10. Stefan XenosFeb 15, 2019
  11. Junio C HamanoFeb 15, 2019

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.