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

atomic commit across multiple projects

From: wing.hon.lai <wing.hon.lai_at_capetechnologies.com>
Date: 2004-12-16 17:06:28 CET

As a Simon Tatham described in his website at
http://www.chiark.greenend.org.uk/~sgtatham/svn.html on section 7.4, it's
possible to make Subversion check-in changes made in different modules with
the same change-set and thus they share the share revision number. I think
this is quite useful especially to identify a change or bugfix that went
into multiple modules for a project. But because it's such a roundabout way
of doing things that I am wondering if this will make subsequent subversion
commands on that revision number or files behave abnormally. Can anyone see
any bad side effects this will have? Will Subversion eventually support this
behaviour without using this workaround?

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Received on Thu Dec 16 17:09:25 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.