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

Re: Committing file and directory moves

From: Blair Zajac <blair_at_orcaware.com>
Date: 2006-08-18 04:28:51 CEST

On Aug 17, 2006, at 4:52 PM, Rob Wilkerson wrote:

> Is there any sort of rule-of-thumb for when/how often to commit? I
> have a project - just starting with Subversion - in which I want to
> import the current code base and then do a pretty significant
> reorganization of the code. I want the original code base to start so
> that future maintenance can be done against the Subversion repository
> rather than VSS, our current source control application.

I commit after every logical change that keeps the code working.

> I've now tried this twice and have ended up having to blow up the
> entire repository and start over because of one error or another. It
> seems like Subversion gets confused when too much is going on? Is
> that possible? I was trying to work such that, at any given moment,
> the branch I was working was "stable" with each commit.

No. Look at the kde and the Apache svn repositories:


They have 574,000+ and 432,000 revisions respectively.

> How do others work? Do you care whether the trunk or branch you're
> working on is stable from commit to commit? Any best practice insight
> would be appreciated. I've learned a lot in my mistakes, but I'm
> tired of redoing my work. :-)

Yes, I do that. You can also use continous integration tools to
ensure that each commit keeps the code in shape that passes all the
test suites.


Blair Zajac, Ph.D.
Subversion training, consulting and support
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Aug 18 04:30:42 2006

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.