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

RE: Commit hooks and control of bad development practices?

From: Kevin Williams <kevin_w69_at_hotmail.com>
Date: 2004-05-25 21:19:11 CEST

>I see the critical points as these:
>1. All changes are "assigned" to a developer.
>2. The code they change must be "current".
>3. The code they check back in must be the code they were assigned.

Perhaps the locking feature (not yet released, work in progress) would solve

If I understand correctly, #2 and #3 would be in conflict if #1 is not
enforced because someone else could have updated that code, making the
"assigned" code no longer the "current" code. Is that correct?

Because you have someone checking the incoming code, I suggest you put the
"Id" keyword in a comment in the file. This way the version given to the
developer is noted and can be verified upon return.



To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue May 25 21:20:12 2004

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.