RE: why does my SVN client process die an hour after completion of commit?
From: Jon Nicoll <jnicoll_at_hanoverdisplays.com>
Date: Fri, 21 Oct 2011 13:06:21 +0100
Hi Stefan, Philip
Thanks for your postings:
> On Fri, Oct 21, 2011 at 10:34:52AM +0100, Jon Nicoll wrote:
The reason it happens after a commit is complete on the server is that the client has to modify the metadata for all the items in the working copy that were committed. When the commit starts the items being committed all have local modifications of some kind, when the commit is complete they must all be change to unmodified. This can involve a lot of work, writing pristine text and properties, updating the revision numbers. This updating cannot happen until the client knows that the commit was successful.
====
Ah, that makes sense, thanks.
So for now I would be best off to regard my 'initial working directory' as suspect, and if I checkout from the server into a new directory, that directory should be correct, yes?
(this commit of a large number of files is not something I will have do very often, if at all, after this initial commit).
I'm using SVN client v.1.5.4 BTW - a bit older that I expected. I will also look into getting this updated to 1.7.
Thanks & Regards
Please consider the environment before printing this email
If you received this in error, please contact the sender or postmaster (postmaster_at_hanoverdisplays.com) and delete the material from any computer.
Although we routinely screen for viruses, addressees should check this e-mail and any attachment for viruses. We make no warranty as to absence of viruses in this e-mail or any attachments.
Our Company's email policy is to permit incidental personal use. If this email is of a personal nature, it must not be relied upon as expressing the views or opinions of the company.
|
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.