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

Re: TortoiseMerge cannot diff when files are locked for write

From: Oto BREZINA <otik_at_printflow.eu>
Date: Mon, 14 May 2012 11:11:45 +0200

On 2012-05-14 9:55, Josh Green wrote:
> Hi Guys,
> The Lock is applied with the following line:
> (C#, .NET)
> fileStream = new FileStream(
> fullPath,
> FileMode.OpenOrCreate,
> FileAccess.ReadWrite, FileShare.Read);
> with regard to this:
> "In other words It would solve that issue, but would quite possibly other one."
> What is the other issue it would create?
This what Stefan wrote in some previous mail in this thead

That would mean allowing others to write to the same file we want to
read from. That could lead to inconsistent data read from the file and
then to a completely wrong diff.

Not sure if that would be ok since I don't know of any way to detect that.

> Currently I can already write to the files using another program that Merge is diffing and cause the displayed information to be wildly out of date, I do it all the time, often TortoiseMerge will be running with 10's of stale files for days on end (I often don't get around to closing them)
> Alternatively, the lock mentioned above might be too strict, but like I said, It does allow text editing applications to read it fine.

Sharing has been extendend in trunk you are welcome to try it. I guess
change detection would not work very good in this case.

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2012-05-14 11:12:13 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.