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

Re: using NTFS ADS, HFS+ ResourceForks or other file system metadata facility instead of a .svn directory

From: <Ruediger.Dohna_at_oxaion.de>
Date: 2006-02-13 08:56:50 CET

Julian Foad wrote:
> Could Subversion really, practically, look for an object that has
> disappeared (been moved/renamed/deleted)?

When a file is renamed or moved within the WC, Subversion would see one
file missing from its list of expected files in a directory and another
file showing up, that appears to be new. It could then quickly look at the
meta data of the new file and see if it matches any of the missing files.
Searching the whole file system is clearly not an option.

I had overseen that reverting a deleted file would actually need a server
contact, but I think that would be worth it.

Martin Furter wrote:
> I guess it's much easier to remove the metadat accidently.
> If an application (editor or whatever) writes the data to a temporary
file
> first and then moves it in place the metadata will probably be lost.

Many tools seem to silently overwrite the ADS of a file, including Cygwin
">" and many editors, e.g. EditPad and Eclipse :-(... but not NoteTab and
that often scolded Notepad. I'm not shure if they (esp. Cygwin stdout
redirect) all use temp files or if this is a Windows "feature". This does
not happen with MacOS resource forks, but until a smarter version of
Windows gets widely accepted or at least a majority of Windows tools work
around to maintain metadata, the whole idea is actually a really bad one...
for files! On Windows it could still be feasible to simply move the .svn or
_svn directory into a directory-ADS now and think about file-ADSes later.

And for the more conceptual discussion: Many editors on the Mac use the
resource fork to store things like the current selection/cursor position
and e.g. the versioning system Apple used and offered in the early 90ies (I
forgot its name) used it for the revision number etc. Conceptually this is
a very clean way of doing things, I think: Store file meta data with the
file, so it (ideally) never can get disconnected. Many discussions on
future file systems seem to result in a decision to include a custom meta
data facility.

Does the "sacred" state of a file include its meta data... attatched or
not? Does the "sacred" state of a directory exclude the .svn directory?
Subversion specific meta data would get removed, when you do an export, of
course.

Regards
  Rüdiger

Besuchen Sie uns auf der CeBIT in Hannover vom 09. - 15. März 2006.
Sie finden uns in Halle 5, Stand A38.

This message is intended for the addressee or its representative only.
Any form of unauthorized use, publication, reproduction, copying or
disclosure of the content of this e-mail is not permitted. If you are not
the intended recipient of this e-mail message and its contents, please
notify the sender immediately and delete this message and all its
attachments subsequently.

oxaion ag
Received on Mon Feb 13 08:56:57 2006

This is an archived mail posted to the Subversion Dev mailing list.

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