Stefan Küng wrote:
> Harun Vos wrote:
>> Hi all,
>> I've found an unexpected behaviour when tsvn-deleting a folder
>> containing unversioned or modified files, using 1.6.2 32bit.
>> I have a test repo containing:
>> 1. In subdir in the working copy, I create an unversioned file
>> 2. I right-click on subdir, then TortoiseSVN -> Delete. A prompt asks
>> "The folder <path>\subdir contains unversioned and/or modified file(s).
>> Do you want to remove it anyway?" with Yes, No and Yes to all buttons.
>> 3. I choose "Yes" (or "Yes to all").
>> The entire subdir is deleted - not just emptied and marked as 'to be
>> deleted on commit'. This is odd - "svn delete --force subdir" does not
>> do this.
> But that's not a real problem.
>> At this point, a commit would successfully delete subdir from the repo,
>> To trigger the real problem:
>> 4. I modify the files root1.txt and root2.txt.
>> 5. I commit, and in the commit dialog I deselect root1.txt, root2.txt or
>> The commit fails with "Error: Entry for '<path>\subdir' has no URL".
>> If both root1.txt and root2.txt had been selected for committing, then
>> the commit would have succeeded.
> This is the problem: it's not possible to commit a folder deletion
> non-recursively. And since you excluded at least one item from being
> committed, TSVN is forced to do a non-recursive commit.
Is it possible to change the remove-directory behaviour to match that of
an unmodified directory (or the commandline)?
In that case, it does work as expected, even when excluding items.
>> I have not tested this with the latest nightly (today's - rev 16458 - is
>> missing) so sorry if this has already been fixed.
> Sorry, I broke the build yesterday.
> I'll have a look at this, maybe I can improve the situation a little bit.
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-05-28 04:38:27 CEST