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

problem: move --force with commit --non-recursive

From: Gerco Ballintijn <Gerco.Ballintijn_at_cwi.nl>
Date: 2004-04-23 15:26:23 CEST

I came across the following problem. On the one hand I like to to control
precisely what is committed, but on the other hand the client interface
only allows you to specify recursion on or off for all resources. I'm
therefore specifying all resources explicitly, but this unfortunately
fails when you first do a forced move and then a non-recursive commit.
The following script explains the scenario:

#! /bin/bash

set -x

# setting this up


rm -rf /tmp/repo /tmp/testing
svnadmin create /tmp/repo
svn mkdir -m "" $R/testing
svn checkout $R/testing /tmp/testing

pushd /tmp/testing/

mkdir -p my/pkg/src my/pkg/dst
echo "aap" > my/pkg/src/afile
svn add my
svn -m "" commit my

echo "noot" >> my/pkg/src/afile
svn move --force my/pkg/src my/pkg/dst/src

# fails on .../afile
svn commit -m "" -N my/pkg/dst/src my/pkg/dst/src/afile my/pkg/src

# doesn't commit .../afile
svn commit -m "" -N my/pkg/dst/src my/pkg/src
svn status -v my


set +x

Is this a (known) bug? I need this to properly do a package-rename
refactoring in eclipse (subclipse currently does two separate commits).

G.C. Ballintijn

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Apr 23 15:26:48 2004

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

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