> On 11.12.2013 20:19, Bob Archer wrote: > >> On 11.12.2013 17:21, Mark Kneisler wrote: > >>> I think making the pristine files optional would work for me. > >>> > >>> > >>> > >>> Here’s an idea. > >>> > >>> > >>> > >>> Instead of having pristine copies of all files, how about adding to > >>> the pristine directory only when a file is changed? > >>> > >> You know, that's a great idea! I wonder why we never thought of it > >> ourselves? :) > > Wouldn't that mean that you need to have some daemon service (or file > watcher or something) running to determine if a file is modified? > > Yes. > > > Also, it would mean you would need a constant connection to the server to > use a subversion working copy. > > Not necessarily; we don't need a pristine copy to check if a file is > modified, or > if 's out of date WRT the repository. But the former problem (requiring a > daemon) is already a non-starter.
Right, but if a file is modified you would need to contact the repository to get the pristine because you are going to get an event "after" the file is modified. There may be some transactional file systems that allow you to get an event before the modification is committed to the file system so you can access the original copy, but I think they are few and far between. (So I guess your original response of "great idea" was sarcastic and I didn't see it.) BOb