"Jason Winnebeck" <email@example.com> writes:
> I restructured a repository from a "normal" layout to a
> "trunk/tags/branches" layout, but now annotate shows as if the entire
> file was updated by myself on almost all files.
> The repository was just converted from SourceSafe, using the excellent
> vss2svn script. That process seemed to work as good as expected. So
> then, I wanted to immediately restructure the projects to have a
> "trunk/tags/branches" format. However, this seems to have broken
> annotate somehow. What happens is that I am shown as the latest author
> on all lines with the revision number being the number of the move, on
> almost all files. But **some** files show the annotate as expected. Also
> the log of the move showed a lot of A, D, and M statuses, and when
> committing it took a long time for "sending file data." The size of the
> transaction in the FSFS is 6MB, but I thought copies were "free" in SVN.
> This is why I am thinking I might have done something wrong.
> The two interesting points are that the last line of the files show a
> different author, and that the only changes in the files were in the
> $Revision$ keyword expansion.
> I used the following shell script on the root directory of each project
> in the repository:
> cd "$1"
> svn mkdir trunk
> for x in *; do
> if [ "$x" != "trunk" ]; then
> svn mv "$x" trunk;
> svn mkdir branches
> svn mkdir tags
> My goal was to move all files at the root into a new directory trunk,
> then create an empty branches and tags directory (I decided not to
> import labels).
> One of the reasons to switch from VSS was to have working annotate
> support. Not having the history proper on the files is defeating the
> point of the huge effort to convert the VSS history rather than just
> importing the "tip."
This is a bug in Subversion:
I'll bet that the annotate history is wrong on the files that were
directly renamed, and correct on files that are somewhere underneath
directories that got renamed.
It might be worth re-doing the import; I don't know how much effort
that would be for you.
Sorry not to have a better answer for you. We'd all like this fixed,
but it's a matter of resources.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Mon Jul 9 22:25:56 2007