Adding project to repository seems to break atomic commit

( SVNSCC , VS .NET, Latest, WIN 2000/XP )

Type: Public Status:Closed Created: 30 Mar 06 03:00 Updated: 30 Mar 06 03:00

--> Igor Pushkov (admin) at 30 Mar 06 03:00 writes

You are right, but unfortuantly this cannot be changed. We cannot control
the commit (check-in) sequence because this is controlled by IDE (VS.NET).
It asks us to check-in solution file, than may be project and so on. All
that we can do we did.
However such issue usually appears only on the initial checkin. Later
check-in of changes usually not cause such issue. And any way this is not
critical, you can forget to commit all files at once even by hand.

--> Sean Aitken (user) at 30 Mar 06 03:00 writes

After adding a web project to a repository, I looked at the repos and see
that all the files have varying revision numbers. It seems that the number
is different for each folder and files within. One real benefit of using
SVN is it's atomic commits. From this observation, adding a project with
SVNSCC breaks that model. Is this my imagination, or is this really the
case?

Marking as high since this is a fundamental feature of SVN thats being
comprimised.

See attachment for the different rev numbers.

Showing varying rev numbers after an import of a project

Rate this ticket:

Not useful at all

Partially useful

Useful

Very useful

Ticket

Adding project to repository seems to break atomic commit