Thanks for all the answers here. It appears that my colleague, who is a
competent developer, is not doing something needed to carry over history
for his moves.
Let me ask this: if I move "path1/A" to "path2/A" and then rename
"path2/A" to "path2/B" before doing a commit, is Subversion smart enough
to know that a "delete path1/A, add path2/B with history from path1/A"
operation has occurred? Or must I first commit my "svn move path1/A
path2/A" operation before I perform a "svn rename path2/A path2/B"?
Garret
Ryan Schmidt wrote:
>
> On Jun 30, 2008, at 22:56, Garret Wilson wrote:
>
>> [snip] I just wanted to find *any* way to verify that a file has
>> history. I think the easiest answer seems to be:
>>
>> 1. Do a "svn log repo/trunk/new".
>> 2. If you don't see the history of repo/trunk/old, the history isn't
>> there, because "svn log" by default shows all history.
>
> Yes.
>
> If you use the verbose flag on svn log, you'll also see which paths
> were affected, and for copied paths, which paths they were copied
> from. For example:
>
>
> $ svn log -v http://svn.collab.net/repos/svn/tags/1.5.0/ --limit 1
> ------------------------------------------------------------------------
> r31785 | hwright | 2008-06-19 00:44:46 -0500 (Thu, 19 Jun 2008) | 1 line
> Changed paths:
> A /tags/1.5.0 (from /branches/1.5.x:31699)
> M /tags/1.5.0/subversion/include/svn_version.h
>
> Tagging 1.5.0 with svn_version.h matching tarball.
> ------------------------------------------------------------------------
> $
>
>
> You can see that the 1.5.0 tag was copied from the 1.5.x branch. If
> you omit the --limit 1 option, you get history back through the
> branch, and back through when that branch was originally copied from
> trunk.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-07-02 23:20:46 CEST