Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to email@example.com.
On Mon, Mar 24, 2008 at 1:04 AM, Nick Radov <nradov at axolotl.com> wrote: > > If each developer have its own version of code - they will be getting > > merge > > conflicts if they modify the same file, diffs will be unusable, etc. > > That would only be a problem if they reformat the whole file. It looks like you are not a developer - that explains all your wishes. Actually, they would reformat the whole file - all IDEs have special keyboard shortcut for it. And developers who are care about formatting use it or turn on the "format on save" option. > It would be unfortunate if there is no way to do that within CVSNT. Oh > well, > we are already considering switching source-code control systems anyway > for > other reasons. > Version control systems are designed to keep sources and not to modify them. With ANY source control system you should be able to write a post-commit hook to save the list of modified files and start a new process with a short delay (to let the server finish the commit operation and release locks). E.g. 1 second later the new started script would update the sandbox on server, reformat modified files and commit the new version of them. It has some disadvantages: - 2 committed versions - modified files are not sent back to the client - developer should update the just committed files or he will get conflicts before next commit. Btw, in Subversion there is nothing special to modify the files - only post-commit way. Alex