RE: How to track changes with subversion

One approach is "naming conventions." I.e., have rules the entire team
follows that includes the trouble ticket number and
other information in a prescribed format so you can
easily do history searches.

-----Original Message-----
From: ying lcs [mailto:yinglcs@gmail.com]
Sent: Tuesday, January 16, 2007 11:40 AM
To: users@subversion.tigris.org
Subject: How to track changes with subversion

Hi,

I have a general question about how to track changes with subversion.
Let say I have a trouble ticket #2. I check out the trunk from
subversion. And after I am done with my changes , I call 'svn commit'
and subversion will create a 'revision'.

$ svn commit -m "Fix #2. Switch to use relative path"

Sending sample/changeToOffical.sh
Sending sample/changeToStandAlone.sh
Transmitting file data ....
Committed revision 8.

But what 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.

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

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jan 16 19:02:03 2007