[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

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

From: Grant Edwards <grante_at_visi.com>
Date: Fri, 30 May 2008 18:14:24 +0000 (UTC)

On 2008-05-30, Les Mikesell <lesmikesell_at_gmail.com> wrote:

>>>> 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
>>
>> I'm pretty sure I didn't do that (I wasn't aware you could do
>> that).

[...]

> I don't understand how a copy to create a branch can also
> include newly created files unless the source of the copy is
> the workspace.

Good point. The log definitely shows them happening with a
single commit. If copying from a workspace is the only way that
could happen, then I must have done it that way -- which would
be odd, since that's certainly not the way I normally do it.

> Otherwise you should have a revision # for the creation of the
> branch copy and at least another revision for the commit where
> files were added.

There's only a single log entry that shows the new branch and
the addition of the new files in that branch. I believe I
posted the excerpt from the log showing that somehwere up the
thread, but I can post it again if it would illuminate anything.

-- 
Grant Edwards                   grante             Yow! Send your questions to
                                  at               ``ASK ZIPPY'', Box 40474,
                               visi.com            San Francisco, CA 94140,
                                                   USA
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-05-30 20:15:04 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.