I'm assuming you mean the other developers - the ones who did not modify the code for a specific issue. Yes, they would then have to manually grab the latest revision (whether it be HEAD or some variation of a "current build" tag). For example, in Eclipse/SVN, you go to the "Team > Update" selection on your project. This then downloads any file that has a different version (on the same tag) than the one on your disk. So if you pulled down your working copy a week ago and ten files had been committed since then, that command would pull down all ten files.
I'm not sure if this is a feature that you see as a con, but since the procedure takes about 2 seconds to complete, it's not something to be concerned about. Steve Brownlee http://www.fusioncube.net/ -----Original Message----- From: Claude Schneegans [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 27, 2006 5:28 PM To: CF-Talk Subject: Re: Simple source control >>1. Lock the file (noted on the server) >>2. Download the HEAD revision - the latest copy of the code - in case >>someone else has changed it since their last download >>3. Start working on their job >>Then once they are finished with their files, they commit them. This >>does two things... >>1. Releases the lock on the server >>2. Makes the file read-only on their working copy again This is almost how I imagined it. The only thing, do they have to look by themselves for the new things to update, or is this automatically done during some login procedure ? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Create robust enterprise, web RIAs. Upgrade & integrate Adobe Coldfusion MX7 with Flex 2 http://ad.doubleclick.net/clk;56760587;14748456;a?http://www.adobe.com/products/coldfusion/flex2/?sdid=LVNU Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:265175 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
