Re: Forcing complete binary file comparison for checkin

On Feb 4, 2008 10:34 PM, Lasse Vågsæther Karlsen <lasse_at_vkarlsen.no> wrote:
> Not really commenting on how subversion would or should handle this but IMO
> it's a really badly designed program that modifies a file but hides all
> details about the modification.
>
> Using the date/time stamp is a very typical way to see if a file has been
> modified after a certain point in time.

Unfortunately, with some capture devices (or simply for some of the
less capable consumers of the image files) the only evidence of the
time the image was captured is the modification time of the file - a
poor solution true, but in that circumstance it is understandable that
lossless operations to reorient an image might not want to change the
modification timestamp - of course the reorientation tool probably
shouldn't behave this way by default since most image producers and
consumers add capture information as file-content.

I suppose a new 'svn:inspect-contents' property could be used to
indicate which files need a more expensive contents check and the
working-copy book-keeping could retain a list of those files with this
property to avoid inspecting every files property during a commit,
status or update.

--
Talden
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org