On Jul 25, 2008, at 01:26, AlenWesker wrote:
> As the the title. Everytime there are little mistakes, may it be my
> antivirus soft blocking the access or carelessly clicking "commit"
> once more, the whole directory of our project need to be cleanup,
> no matter how deep or how small the directory where the mistakes
> take place. Do you developers know how to avoid this anoying
> "Cleanup"? Even a hack method is OK. I am enough about it.
>
> SVN works fine if the total amount of project files are within a
> certain limit, and when a project is inflated out of the bound,
> cleanup become an inevitable bottlenet in out development process.
> Looking forward to your help.
>
> By the way, when I am writing this email, the cleanup process is
> just finished, and it has last exactly 32 minutes. Dont ask me why
> out project have so many files, it is just reality.
How many files or more importantly how many directories are in your
working copy?
How are you "clicking 'commit'" -- what GUI are you using?
You can run "svn commit" or other svn operations on just the subtree
of your working copy that you're actively working on. That way
Subversion won't have to spend time looking at other directories that
you already know are unchanged, and if something happens that
requires a cleanup, it will only require a cleanup of that subtree.
But cleaning up should not be needed frequently. I can't remember the
last time I've had to clean up. Months? Years? If you're having to
clean up much more frequently, then maybe there is something that can
be fixed. We just need more info about how you are getting into these
situations. More info about your client, like what OS you use and
what version of Subversion you have, could help.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-07-26 07:49:34 CEST