From: Thomas Adam Date: Sun, 24 Jul 2011 12:16:00 GMT Subject: Re: Help using git I'm review process Message-ID: In-Reply-To: <245B4B40-CA0A-43F6-A3F0-85E50D75CB93@gmail.com> On 24 July 2011 13:12, Mathew Benson wrote: > I'm planning to use git for a work project, which requires tight control of the peer review process.  In previous jobs, the peer review was a tedious manual process of creating PDF files, writing comments in spreadsheets, and copying comments to the CM system.  I want to use technology to my best advantage. > > Once a developer has completed all his changes in his development branch, what's the best way to get those files to the reviewers, without requiring the author to stop work?  First, I think I should create a tag in the developer branch.  Each developer has a local repository, and my review tool writes files directly in the work area.  Can they just fetch, checkout a tag (don't know how to do that), commit changes, and push it back to the central repository?  Is there a better workflow?-- This is what Gerrit is useful for. -- Thomas Adam