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

Re: Working towards a common review format for git

From
Dave Borowitz <dborowitz@google.com>
Date
Jan 8, 2016, 19:26 UTC
Message-ID
<CAD0k6qQLM=Fh_FGU6JN8=52Kjab6AqMfFTaK7DiNYgpWa5nJpg@mail.gmail.com>
In-Reply-To
<20160108192339.GA3514@salo>

On Fri, Jan 8, 2016 at 2:23 PM, Richard Ipsum <richard.ipsum@codethink.co.uk> wrote:

Show 8 quoted lines
>> You know what would probably also be a good idea would be to spec out
>> the entire format in a standalone document. That way when Gerrit
>> doesn't have something implemented, it's clear that Gerrit is wrong,
>> not that it's trying to fork the format.
>
> I think that would be good, I could attempt to write a spec for the format
> and post it here for review? I expect I'll want to work a little more on
> perl-notedb before I do that though.

Sure. I don't want to necessarily make more work for you, but it's probably a good exercise to have someone write a spec who did not also write the first implementation :)

You may post it here but you would probably get more feedback on repo-discuss@googlegroups.com.

Previous: Richard Ipsum
Message 5 of 5 in “Working towards a common review format for git”
  1. Richard IpsumJan 8, 2016
  2. Dave BorowitzJan 8, 2016
  3. Dave BorowitzJan 8, 2016
  4. Richard IpsumJan 8, 2016
  5. Dave BorowitzJan 8, 2016

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.