Concerning Re: Re: Is there really no way to k
Erik Huelsmann wrote on 5 Mar 2007, 12:42, at least in part:
> On 3/5/07, Jan Hendrik <jan.hendrik@myrealbox.com> wrote:
> > Concerning RE: Re: Is there really no way to
> > Thompson, Graeme (AELE) wrote on 28 Feb 2007, 3:52, at least in
> > part:
> >
> > > We have the constant argument that the modification date time is
> > > unreliable, unfortunately this statement is driven by programs
> > > like subversion that throw this information away, thus making the
> > > modification date time unreliable.
> >
> > While at the same time relying on just this - and only on this - for
> > commit!
.... and even update.
> Absolutely not!
>
> Subversion has a heuristic to determine whether it may need to commit
> a file or not. Loosing the mtime (ie damaging) is no problem for
> subversion: the timestamp will have changed and this means the file
> needs to be further inspected to see if a commit is required.
Absolutely yes. If for any reason, deliberately by a tool like recode
or by the user or clock thrift or what else, the mtime has not
changed (was not 'damaged' by editing) an svn update will destroy
any local modification without any kind of warning, merging, or
conflicting, *even* if the filesize has changed as I am just about to
file an issue.
JH
---------------------------------------
Freedom quote:
Dem Kapitalismus wohnt ein Laster inne:
Die ungleichmäßige Verteilung der Güter.
Dem Sozialismus hingegen wohnt eine Tugend inne:
Die gleichmäßige Verteilung des Elends.
-- Sir Winston Churchill
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Mar 6 17:31:16 2007