> I think instead of the database/repository you mean the metadata of the
> workingcopy. You question the is if there is a way to mark the file for
> deletion just from the fact that it has already vanished from the
> workingcopy.
yes - this is what I mean - sorry for my language
>
> There isn't really a way for that. However, there is a feature in
> TSVN that
> when you commit a folder, it offers all missing file, too. From
> that dialog,
> you can directly file the already missing file for deletion.
>
> > I have a particular issue with people swapping between detailed view and
> > thumbnail view in their file system. It seems that this process deletes
> > thumbnails (when switching to details) and if they do not commit these
> > deletions before switching back and re-creating the thumbs.db
> files, there
> > is an annoying error in trying to add a file to the repo which already
> > exists. My auto update then commit script does not bring the
> repo version
> > othe thumbs.db file back to the working copy because the working copy
> > database thinks it's already present, when it's not, but DOES think that
> > the newly created thumbs.db file is a new addition instead of
> an update of
> > an existing file. I thought at first it was a case problem but the OS
> > (WinXP) always uses teh same case Thumbs.db for the file.
>
> Don't version those files, as others already said. You can even tell
> Subversion that it should always ignore these files and disallow
> them even
> stronger via a pre-commit hook.
>
> Uli
thanks - I'll work on this
Alan
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Nov 15 13:58:27 2006