No not yet. I did not have time this evening. I agree that this is
probably the way to go. I wanted to inform you though...
From: Mark Phippard [mailto:email@example.com]
Sent: Mittwoch, 10. Januar 2007 10:36
Subject: Re: [Subclipse-dev] Another bug in new locking code in 1.1.9
On 1/10/07, Thomas M. Hofmann <firstname.lastname@example.org> wrote:
I have built a new version based on head and deployed it to some
co-workers. Today one of them called me because he noticed some
behavior. I had a look and saw that the read only flag was not
after a file was locked (using svnkit). I created a new file and
problem did not occur. I thought about problems with blanks in
filename / path but renaming the new file for testing to a name
balnks still did not show the error. The files already in the
all showed the errornous behavior (all I tried at least).
So this is pretty strange and difficult to pin down. Any ideas?
Have you tried bringing up the issue on the SVNKit mailing list yet?
That is what I would recommend.
Received on Wed Jan 10 22:42:28 2007