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

Re: Re: Problems with SVN Rename

From: Andy Levy <andy.levy_at_gmail.com>
Date: Thu, 1 Apr 2010 09:06:44 -0400

On Thu, Apr 1, 2010 at 08:03, Matthias Lüthi <matthias.luthi_at_gmail.com> wrote:
>
> On Wed, Mar 31, 2010 at 18:55, Matthias Lüthi <matthias.luthi_at_gmail.com> wrote:
> > I'm having problems renaming files in a repository. Here's the step-by-step:
> >
> ...
> >
> > Instead I observe the following:
> >
> > Example.pdf is added to the repository as expected
> > Example.xls is NOT deleted from the repository (Repo browser shows BOTH files and in the changelog there is only an entry for the "added" action of Example.pdf, but no "deleted" for Example.xls)
> > When I update my project to SVN revision x, I don't get a copy of the file at all. When I update to version x+1 though I do get Example.pdf
> > Revision graph and history work fine, i.e. they both show the correct relationship between Example.xls and Example.pdf
> >
> ...
> On 2010-04-01 03:22:10 PDT, Andy Levy wrote:
> >Are you committing at the folder level, or committing the "new" file (Example.pdf)?
> Thanks for pointing this out: I was committing only the file. It would be nice to at least get a warning in such a case of renaming a file, but I guess that's just the way SVN is working. So the rule is: after renaming a file you have to do the next commit at the folder level?

Yes, because you need to record both the delete and the add.

Subversion renames are not "renames" - they're a copy with history
plus a delete. The same is true of moves.

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2468309

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-04-01 15:07:13 CEST

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

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