On 5/25/2011 9:59 AM, Gilles wrote: > For instance, with the repository file at the root of C:\ (so I can > add any file below that, even in sub-directories), trying to add > D:\test.txt triggers the error message: "C:\fossil.exe: not within an > open checkout".
This is correct behavior. If you took your repo and opened it on another computer, either in the c:\ root or in a folder, fossil could restore all the files in exactly the same relation to each other as you had them. They might have a different root or be on a completely different drive, but if you had a file in \foo that referred to ..\bar\otherfile, the reference would still work. But what if you were allowed to add d:\test.txt? What's fossil supposed to do when you open that repo again somewhere else? I don't have a D: drive. Lots of computers have a DVD drive under D:. And even if I have a D: drive, what if I open your repo twice in two different folders on my system? (E.g., assuming it's software, to keep one behaving normally and make my weird changes in the other copy to compare.) So, yeah, all your repo files have to have a common root. It's by design and can't be worked around except by moving files into a common root. (And check out <http://en.wikipedia.org/wiki/NTFS_junction_point>) And you should really think about your entire-c-drive-is-my-working-copy thing. Maybe it makes sense for your use case, but it's at least a very unusual use of fossil. -- Joshua Paine LetterBlock: Web Applications Built With Joy http://letterblock.com/ 301-576-1920 _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
