How to track changes with subversion

Hi there.

I'll have a go at this... I think other's are of the same opinion
anyway.

> [W]hat if I realize my changes is incomplete, the I need to add
> more files. If I do a 'svn commit' again, subversion will create
> a new revision.

> What if there is another person will do a svn commit between my
> 2 'commit's? And when the build person builds a build with just
> my fix, how can he do it ? Since my fix now span in 2 revisions.

I believe that unless changes in a later revision have touched code in
changes made in an earlier revision, SVN should allow the earlier
revision to be backed out without complaint.

Anyway, philosophically...

I try to live by the ethos that one should not do anything (in life,
generally) until one has checked and rechecked that what one is about to
do is at least what one intended.

I like version control because it records everything, including
screwups. In SVN, a developer has a hard time playing the revisionist,
attempting to change history to erase their (most probably innocent, but
wrong nevertheless) wrongdoing. Fortunately also, SVN gives one the
ability to quickly back out changes with confidence that all ones
screwups have been safely removed from the product.

As a more practical measure (one I'm yet to make use of mind you),
another solution to concurrent development might be the art of
'branching and merging'.

Enjoy,

  Owen.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jan 16 23:33:48 2007