From: Thomas Adam <thomas@xteddy.org>
To: Mathew Benson <mathew.benson@gmail.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Help using git I'm review process
Date: Sun, 24 Jul 2011 13:16:00 +0100 [thread overview]
Message-ID: <CA+39Oz5OT_RjyGeQdKaFycHjwN6hzy+N6P6DDBAtSv3vTYo_4A@mail.gmail.com> (raw)
In-Reply-To: <245B4B40-CA0A-43F6-A3F0-85E50D75CB93@gmail.com>
On 24 July 2011 13:12, Mathew Benson <mathew.benson@gmail.com> 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
next prev parent reply other threads:[~2011-07-24 12:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-24 12:12 Help using git I'm review process Mathew Benson
2011-07-24 12:16 ` Thomas Adam [this message]
2011-07-24 12:42 ` Mathew Benson
2011-07-24 12:53 ` Thomas Adam
[not found] ` <E394E5A1-8F0E-47E6-AE69-A974655B2D13@gmail.com>
2011-07-24 14:02 ` Fwd: " Thomas Adam
2011-07-24 14:19 ` Mathew Benson
2011-07-24 15:40 ` Fwd: " Magnus Bäck
2011-07-24 14:37 ` Jens Lehmann
2011-07-24 15:32 ` Mathew Benson
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=CA+39Oz5OT_RjyGeQdKaFycHjwN6hzy+N6P6DDBAtSv3vTYo_4A@mail.gmail.com \
--to=thomas@xteddy.org \
--cc=git@vger.kernel.org \
--cc=mathew.benson@gmail.com \
/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).