Re: How to compare working copy file with older version of that file?

Grant Edwards wrote:
>
>> Did you create the branch, delete it, then create it again?
>
> No, not that I remember, and I don't see any indication of that
> in the log for the parent directory.
>
> It appears from the log that I committed both the "copy"
> operation that created the branch and the additions of the new
> files in a single "commit". Is that illegal?

If you copy workspace -> URL you can get changes in the copy that aren't
committed anywhere else - and sometimes you might want that.

> I guess I can create a new branch from the trunk and re-add the
> current versions of the new files. Assuming that new branch
> isn't broken, I'll at least have access to revisions from this
> point forward. I won't have history on the added files prior
> to today, but by access to old revs of those files isn't really
> working anyway.

If you expect the start of a branch to have continuous history back
through the trunk before the branch was created, you need to either
commit all changes back to the trunk before copying the workspace to a
branch or create the branch by copying a trunk revision instead of the
workspace.

-- 
   Les Mikesell
    lesmikesell_at_gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org