[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: subversion and code peer reviews

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2005-01-13 23:55:22 CET

On Jan 13, 2005, at 4:33 PM, Geoff Krapf wrote:

> It seems like "svn status" would work fine. That shows which files
> have
> been modified in the working copy.

Most subversion teams also set up the repository to send email
everytime somebody commits. The email contains unified diffs of the
changes, so peers review the changes after they're already committed.
Discussion happens on email, and after receiving feedback, the original
committer goes and makes more followup changes.

This assumes, of course, that everybody trusts one another. "Commit
first, get feedback second." If your company is really paranoid, then
people can commit to private branches. People will still be able to
review the changes in email, and after feedback is done, the changes
can be merged from the branch to the main 'trunk'.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jan 13 23:58:51 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.