Ralph Seichter wrote on Thu, 19 Oct 2017 18:31 +0200:
> On 19.10.17 18:17, Daniel Shahaf wrote:
>
> > Subversion doesn't use checksums to detect modifications. 'svn status'
> > is based on filesize + mtime only.
>
> I seemed to remember subversion behaved like git in this regard, using a
> checks
On 19.10.17 18:17, Daniel Shahaf wrote:
> Subversion doesn't use checksums to detect modifications. 'svn status'
> is based on filesize + mtime only.
I seemed to remember subversion behaved like git in this regard, using a
checksum (as shown in 'svn info') as an indicator, rather than raw file
si
Ralph Seichter wrote on Thu, 19 Oct 2017 13:01 +0200:
> On 19.10.2017 12:16, Sasikala Kottegoda wrote:
>
> > In this scenario, svn status does not show anything. Also, the file
> > does not get commited when I issue an 'svn commit'. Is there a reason
> > for that?
>
> Subversion uses a hash of th
On 19.10.2017 12:16, Sasikala Kottegoda wrote:
> In this scenario, svn status does not show anything. Also, the file
> does not get commited when I issue an 'svn commit'. Is there a reason
> for that?
Subversion uses a hash of the file content to determine if it has been
modified. Changing the mo
Hi Andreas,
Thanks for the prompt reply.
In this scenario, svn status does not show anything. Also, the file does
not get commited when I issue an 'svn commit'. Is there a reason for that?
Thank you,
Sasikala
On Thu, Oct 19, 2017 at 3:25 PM, Andreas Stieger
wrote:
> Greetings,
>
> On 10/19/20
Greetings,
On 10/19/2017 11:41 AM, Sasikala Kottegoda wrote:
> A file named a.txt exists inside a folder in the working copy, which
> has been copied from somewhere else
>
> * cCopy and replace a.txt with the same file/or modify it by issuing
> the 'touch' command
> * Do an svn status, it
