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

Re: CleanUP Command is horrible

From: Ryan Schmidt <subversion-2008c_at_ryandesign.com>
Date: Mon, 28 Jul 2008 05:24:00 -0500

I don't have an answer for you Alen; I'm sending your message back to
the mailing list where hopefully someone else will respond.

On Jul 27, 2008, at 22:40, AlenWesker wrote:

> Ryan Schmidt wrote:
>> 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.
> Thank you very much for your reply. The SVN version infos are
> listed below.
> TortoiseSVN 1.5.0, Build 13316 - 32 Bit , 2008/06/21 07:55:29
> Subversion 1.5.0,
> apr 1.2.12
> apr-utils 1.2.12
> berkeley db 4.4.20
> neon 0.28.2
> OpenSSL 0.9.8g 19 Oct 2007
> zlib 1.2.3
> OS: windows XP, SP2, Dell OEM edition
> We currently have 10G files in out product directory, which is
> totally SVN managed, including all of our textures, model files and
> large binary files, brabra. Sounds crasy...
> The "Clean Up" symption will reappear like this : If one file has a
> system lock(It may be caused by opening the file, your application
> being reading or writing on it, or your antivirus software being
> working on it), you click "SVN Update", a red report pop up when
> the update process goes to that file, then the whole directory need
> to be "CleanUP", and any SVN operation is forbidden, prompt that
> "CleanUp" is needed. Hower, system lock is too difficult to be
> avoided, unless you stop all the works when updating. Nearly all
> of my colleague have experience the scene discribed above, and then
> the "CleanUP" operation take them half an hour.
> Another case is that when I commit a directory, I am too impatient
> to wait for the process to be finished, and I try to commit a sub
> directory which is much smaller, but it also cause "Cleanup" prompt.
> There are some other ways to "summon" the red "CleanUp", I can't
> remember all of them.
> I think you have figure out what the problem is. As one of my
> colleague said, SVN is not designed for resource control, but code
> control.
> Anyway, is there something we can do to suppress the cleanup
> requirement? We know exactly where the error takes place when it
> happens, and we dont want to make a recursive cleanup through the
> whole directory.
> There's one little piece of suggestion: why doesn't SVN have an
> option of "clean update" in the "update" panel? And that is
> supported in CVS. "Clean update" is very useful, when I find out
> that my changes are useless in a file, I just "clean update" it to
> a fine state. I know that in SVN, I can "reverse", then "update".
> But a "clean update" is surely more convenient, and it is not
> difficult to implement at all, right?

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-28 12:24:40 CEST

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.