cc-ing the group.. i did not hit 'reply-all' first time..
On 8/24/07, Mark Eramo <firstname.lastname@example.org> wrote:
> I am having a problem with Subversion and wondering if anyone has run
> into this before. ( I am rather new to Subversion so I am not sure if
> this is a bug or I am doing something wrong).
> We are using Subcommander 1.2.2 as our GUI Interface. Here is the issue.
> I check out the following folder/code from the Subversion Repository:
> Now the code is on my local PC. When I setup a working copy folder, it
> shows up fine in subcommander.
> I put the code into in */home/user/Subversion/Database/project1 (mind
> you, the code in trunk resides i nthe project1 folder so there ie now
> trunk sub folder).*
> A developer came along and added the following folder into Subversion:
> *So now there is a test cases folder under trunk with new code.
> I now go into Subversion and checkout the *test cases only*, not all the
> code under trunk.
> They would get checked out to:
> *If I then look at the working copy view in Subcommander, it is like
> Subversion does not know I have it checked out there. In Subcommander,
> the folder test shows up with a question mark. Subversion does not see
> them as being under source control but I just checked this out from the
> repository. The test folder has it's own .svn folder now and the code is
> in the test folder.
> If I start over and do a recursive checkout on the trunk folder to
> include all the files in test as well, it shows up fine in subcommander.
> It is almost like subversion is not updating the information in the*
> /home/user/Subversion/Database/project1/.svn* folder to tell it about
> the new folder/code the I just checked out underneath.
> I was wondering if anyone has run int this? Could this be a subversion
> or subcommander bug? Could I be doing something wrong, missing a step?
> Any help or thoughts would be much appreciated.
I believe you just checked out the project1/trunk/test folder under
project1/ folder. Those are two different checkouts and svn will treat them
that way. The only reasons .svn folder gets updated are when you check-in
something from your folder or when you update ('svn up') that folder.
So, basically, if you update project1, instead of checking out a folder
separately, you will be fine.
Received on Fri Aug 24 21:10:03 2007