From: Richard Ipsum <richard.ipsum@codethink.co.uk>
To: Andreas Krey <a.krey@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: Code review tool recommendations - replacement for crucible?
Date: Thu, 16 Jun 2016 11:55:56 +0100 [thread overview]
Message-ID: <20160616105556.GA8721@salo> (raw)
In-Reply-To: <20160616094108.GA14661@inner.h.apk.li>
On Thu, Jun 16, 2016 at 11:41:08AM +0200, Andreas Krey wrote:
> Hi all,
>
> I'm looking for pointers to review tools that work with git (obviously),
> and can deal sensibly with bigger reviews. Things we need:
>
> - Ability to split (set of) commits into multiple reviews,
> so parts of changes can be reviewed by the respective owners
> (or assign different reviewers to different files/subtrees
> in a review).
>
> - Tracking of files (or changes) already reviewed (due to the large numbers),
> and of the handling of issues found so far.
>
> - Support incremental reviews, not just e.g. over the content of a
> pull request (bitbucket) When review comments are processed people
> want to be able to only review that change, and not to be forced
> to find that change in the entire previous changeset without
> the tool's support.
>
Hey,
Have you considered Gerrit[1] already?
It would seem to handle the cases you're interested in.
[1]: https://gerrit-review.googlesource.com/Documentation/
next prev parent reply other threads:[~2016-06-16 10:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-16 9:41 Code review tool recommendations - replacement for crucible? Andreas Krey
2016-06-16 10:55 ` Richard Ipsum [this message]
2016-06-16 12:14 ` Andreas Krey
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160616105556.GA8721@salo \
--to=richard.ipsum@codethink.co.uk \
--cc=a.krey@gmx.de \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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.
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 NNTP newsgroup(s).