Re: WebDAVFS and Dreamweaver

[Ben Collins <bc...@debian.org>]

> Putting a new file works, but the O.S. also puts a file of _filename in as
> well.  When I use the Finder to put a file, the OS later deletes _filename.
> 1 Change and 3 revisions (put filename, put _filename, delete _filename).
> When I put a new file using Dreamweaver, for some reason the _filename
> doesn't get deleted.  1 Change, 2 revisions, and 1 extraneous _filaname file
> left in the repository.

FYI, the _filename is the resource fork. I suspect Dreamweaver has a
resource fork in it's files, so that's why it gets left. I notice this
with a standard WebDAVfs on my MacOS X.

-- 
Debian     - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
Deqo       - http://www.deqo.com/

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: WebDAVFS and Dreamweaver

[Chris Parker <su...@playswithfire.com>]

On Thu, May 01, 2003 at 12:19:00AM -0400, Ben Collins wrote:
> FYI, the _filename is the resource fork. I suspect Dreamweaver has a
> resource fork in it's files, so that's why it gets left. I notice this
> with a standard WebDAVfs on my MacOS X.

Mac OS X does this with any resource fork and some other metadata when
the target filesystem is seen on its end as "flat" (Which right now is
just a fancy way of saying "Not HFS+" - so NFS, SMB, etc...).

It's an unfortunate "lowest common denominator" compromise, since in
some cases (i.e. WebDAV) there's actually a place for that kind of
metadata and information that would be -just fine- but it's not used.

.chris

-- 
Chris Parker
Objective C: 'cause [ and ] aren't just for array dereferencing
anymore...

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org