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

Re: Code review tool recommendations - replacement for crucible?

From
Andreas Krey <a.krey@gmx.de>
Date
Jun 16, 2016, 12:14 UTC
Message-ID
<20160616121419.GQ30134@inner.h.apk.li>
In-Reply-To
<20160616105556.GA8721@salo>

On Thu, 16 Jun 2016 11:55:56 +0000, Richard Ipsum wrote: ...

> Have you considered Gerrit[1] already?
> It would seem to handle the cases you're interested in.
Possible, but only after a lot of user education.

We don't currently rewrite commits for review comments, and neither can we get (all) people to create feature-oriented commits, so we really need to review multiple commits in one review, and assign reviewers to subtrees. We could do that by repacking the changes into new commits, but that would defeat the purpose.

Also, we often do reviews after feature integration, and also do partial reviews long before a new project is integrated.

In other words: Lots of impedance mismatch.
Andreas
-- 
"Totally trivial. Famous last words."
From: Linus Torvalds <torvalds@*.org>
Date: Fri, 22 Jan 2010 07:29:21 -0800
Previous: Richard Ipsum
Message 3 of 3 in “Code review tool recommendations - replacement for crucible?”
  1. Andreas KreyJun 16, 2016
  2. Richard IpsumJun 16, 2016
  3. Andreas KreyJun 16, 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.