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

Re: How to track changes with subversion

From: Ryan Schmidt <subversion-2007a_at_ryandesign.com>
Date: 2007-01-16 20:34:36 CET

On Jan 16, 2007, at 11:39, ying lcs wrote:

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

If it's important to your development style that multiple changes
that were committed to fix a bug are testable in isolation of any
other changes, you may want to use a branch to perform the bugfix.
Then, once it's been tested and accepted, you can merge it to the trunk.


The questions you've been asking are fairly basic questions that are
all explained in the book. I recommend you take a few days to read it
thoroughly from the beginning; it should improve your understanding
of how Subversion can be used.


To reply to the mailing list, please use your mailer's Reply To All  
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jan 16 20:36:19 2007

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.