Re[2]: Rename + Change in one commit

[Lev Serebryakov <le...@serebryakov.spb.ru>]

Hello Ben,

Friday, August 29, 2003, 7:45:17 PM, you wrote:

>>   svn move Old New
>>   ${EDITOR} New/module.pm
>>   svn ci
>>   I got error.
BCS> This should not error.  Show us details, so we can reproduce.
 Easy. Really, there are TWO level of renames. May be it is point:

 svn rename Old New
 svn rename New/Old2ndlevel New/New2ndlevel
 ${EDITOR} New/New2ndlevel/Module.pm
 svn ci -m "Test"

Adding         trunk\New
Deleting       trunk\New\Old2ndlevel
Adding         trunk\New\New2ndlevel
svn: Filesystem has no item
svn: Commit failed (details follow):
svn: file not found: revision `32', path `/project/trunk/New/New2ndlevel'

  But I need such rename. Is it possible? Rename in two steps (two
  commits) is bad idea :(


-- 
Best regards,
 Lev                            mailto:lev@serebryakov.spb.ru


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Re[2]: Rename + Change in one commit

[Ben Collins-Sussman <su...@collab.net>]

Lev Serebryakov <le...@serebryakov.spb.ru> writes:

> Hello Ben,
> 
> Friday, August 29, 2003, 7:45:17 PM, you wrote:
> 
> >>   svn move Old New
> >>   ${EDITOR} New/module.pm
> >>   svn ci
> >>   I got error.
> BCS> This should not error.  Show us details, so we can reproduce.
>  Easy. Really, there are TWO level of renames. May be it is point:

Why did you *say* that?  That's not what your description said!

> 
>  svn rename Old New
>  svn rename New/Old2ndlevel New/New2ndlevel

This will break during commit.  It's a known bug, issue 1259.

The workaround is to commit the two 'moves' independently.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org