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

Re: [PATCH 0/2] git-candidate: git based patch tracking and review

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Dec 1, 2015, 20:55 UTC
Message-ID
<20151201205527.GF18255@google.com>
In-Reply-To
<5643107B.20501@alum.mit.edu>
Michael Haggerty wrote:
> On 11/10/2015 01:56 PM, Richard Ipsum wrote:
Show 11 quoted lines
>> I've continued my work[1] to add patch tracking and candidate review capability
>> to git.
>>
>> git-candidate now has a more git-like user interface, so remote candidates
>> can now be specified in a similar way to remote refs (e.g. origin/candidate)
>> as well as various other improvements, such as versioned metadata.
>
> This is a really interesting project. I've seen a blog post or two
> proposing to store bug tracker information in Git in a distributed way,
> but I don't recall anything about doing the same for code review
> information.

Cc-ing dborowitz, who has been working on storing Gerrit's code review information in Git instead of a separate database (e.g., see [1]).

Thanks, Jonathan

[1] https://storage.googleapis.com/gerrit-talks/summit/2015/NoteDB.pdf
Previous: Junio C HamanoNext: Dave Borowitz
Message 12 of 14 in “git-candidate: git based patch tracking and review”
  1. 0/2 git-candidate: git based patch tracking and reviewRichard Ipsum, Nov 10, 2015
  2. 1/2 contrib: Add git-candidate subcommandRichard Ipsum, Nov 10, 2015
  3. 2/2 contrib/git-candidate: Add READMERichard Ipsum, Nov 10, 2015
  4. David TurnerNov 10, 2015
  5. Richard IpsumNov 11, 2015
  6. David TurnerNov 11, 2015
  7. Sebastian SchuberthJan 6, 2016
  8. Michael HaggertyNov 11, 2015
  9. Richard IpsumNov 11, 2015
  10. Jeff KingNov 14, 2015
  11. Junio C HamanoNov 14, 2015
  12. Jonathan NiederDec 1, 2015
  13. Dave BorowitzDec 1, 2015
  14. Richard IpsumJan 6, 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.