Hi, Contrary to CVS, SVN manages commits as changesets. In practice this means that committing a change where several files are involved should be done in a directory where all affected files reside in that directory or in subdirectories thereof. For example, a change affecting mymodule/inc/file.hxx and mymodule/source/file.cxx should be committed in directory mymodule using the command
svn commit -m"commit message" without specifying file names. Similarly, a change that involves files in different modules can be committed in the root directory of the repository, for example in <yourpath>/ooo Of course you can also commit changes to only mymodule in <yourpath>/ooo, the command needs just more time to complete. Committing all related files in one pass has the advantage that later on one can obtain a list or diff or even merge all affected files by querying one revision number (remember that SVN increments the global revision number with each commit), for example svn log -c revnum -v svn diff -c revnum svn merge -c revnum Because of this it is also a good idea to state in an issue all revision numbers a fix resulted in. Thank you for cooperating ;) Eike -- OOo/SO Calc core developer. Number formatter stricken i18n transpositionizer. SunSign 0x87F8D412 : 2F58 5236 DB02 F335 8304 7D6C 65C9 F9B5 87F8 D412 OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS Please don't send personal mail to the [EMAIL PROTECTED] account, which I use for mailing lists only and don't read from outside Sun. Use [EMAIL PROTECTED] Thanks.
pgp9gZLZi7gTH.pgp
Description: PGP signature
