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

Re: Distributed code review discussion

From
Junio C Hamano <gitster@pobox.com>
Date
Jan 10, 2015, 18:34 UTC
Message-ID
<CAPc5daX2VnikiBOLOSbTuf7QtejV9VRDg-UJKjNQg_6DhUS_Yw@mail.gmail.com>
In-Reply-To
<CAH5CKOqSc2qLZwhCrafYkXMvLmRxKeA_7OO+WzM2FQwKS9F3cQ@mail.gmail.com>
On Sat, Jan 10, 2015 at 10:05 AM, Matus Faro <matusfaro@gmail.com> wrote:
Show 6 quoted lines
> Are there any plans for supporting merge requests and code reviews
> natively in git?
>
> What I mean is a distributed code review system where a merge request
> along with review comments would be stored within the git repository
> and allowed to be pushed and pulled between repository clones. ...

I remember hearing that Gerrit is already going in that direction, except that their plan do not include contaminating the project's real history with the review metadata. You may want to study what they plan to do in order to make yours compatible, if you are planning to write a new one.

Previous: Matus FaroNext: W. Trevor King
Message 2 of 3 in “Distributed code review discussion”
  1. Matus FaroJan 10, 2015
  2. Junio C HamanoJan 10, 2015
  3. W. Trevor KingJan 10, 2015

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.