mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <>
Subject: Re: [PATCH v5 1/8] technical doc: add a design doc for the evolve command
Date: Fri, 15 Feb 2019 10:23:28 -0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <> (sxenos's message of "Thu, 14 Feb 2019 20:30:58 -0800") writes:

> From: Stefan Xenos <>
> 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 <>
> ---

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.

  parent reply	other threads:[~2019-02-15 18:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-15  4:30 [PATCH v5 1/8] technical doc: add a design doc for the evolve command sxenos
2019-02-15  4:30 ` [PATCH v5 2/8] sha1-array: implement oid_array_readonly_contains sxenos
2019-02-15  4:31 ` [PATCH v5 3/8] ref-filter: add the metas namespace to ref-filter sxenos
2019-02-15  4:31 ` [PATCH v5 4/8] evolve: add support for parsing metacommits sxenos
2019-02-15  4:31 ` [PATCH v5 5/8] evolve: add the change-table structure sxenos
2019-02-15  4:31 ` [PATCH v5 6/8] evolve: add support for writing metacommits sxenos
2019-02-15  4:31 ` [PATCH v5 7/8] evolve: implement the git change command sxenos
2019-02-15  4:31 ` [PATCH v5 8/8] evolve: add the git change list command sxenos
2019-02-15 18:23 ` Junio C Hamano [this message]
2019-02-15 22:18   ` [PATCH v5 1/8] technical doc: add a design doc for the evolve command Stefan Xenos
2019-02-15 23:36     ` Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).