Hi SVN Users,
We use svnmerge.py to merge from development
branch to release branch(trunk). We do have many
developers who can perform this merge & commit to
trunk.
It often happens that many commits fail the first
time because someone else has committed & so an
update is required again, and the commit needs to
be reattempted. (i.e., update & commmit need to
be retried many times!) Though this feels like a
normal usage model for SVN, this problem is
exacerbated because every commit is guaranteed to
require an update - reason being the top level
directory has svnmerge-integrated property which
changes with each commit.
How do the current users deal with this issue ?
Uupdate/Commit can take several minutes depending
upon the #files modified, and this turns out to
be
frustrating.
Thanks!
sdotp
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Oct 17 16:22:55 2006