> -----Original Message-----
> From: Peter Davis [mailto:peter@pdavis.cx]
> Sent: Tuesday, December 10, 2002 12:37 PM
> To: Roman Rytov; dev@subversion.tigris.org
> Subject: Re: History of erased file
>
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Tuesday 10 December 2002 02:09, Roman Rytov wrote:
> > it possible to figure out somehow where a.txt
> > became b.txt?
>
> One way would be to use "svn log --strict b.txt" to find out
> where b.txt was
> created, which is presumably the last (earliest) revision
> shown in the list
> of logs. The "--strict" option prevents any logs for
> revisions that existed
> before the copy from being displayed. Use the "--verbose"
> option to make
> sure.
That works fine but only if I know that A.txt became B.txt
Let me introduce an example:
A.txt is created - rev. 1
A.txt is modified - rev. 2
A.txt is renamed to B.txt - rev. 3
B.txt is modifyed - rev. 4 //already no info about A.txt
Looking at the first revision's log I see that A.txt existed. Looking at
the last (4) revision's log I see it doesn't exist. Unless I check out
history of B.txt can I know that A.txt became B.txt? Trace all revisions
in between to find it? It might be boring:-)
Roman
>
> - --
> Peter Davis
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.0.7 (GNU/Linux)
>
> iD8DBQE99cPmhDAgUT1yirARAqnpAJ9/vT/Q7XDQnTdX6A+s6HXOHbkwZgCdEBst
> RQlZVpH7nPtc0idnvIiQXrk=
> =te5R
> -----END PGP SIGNATURE-----
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Dec 10 14:34:49 2002