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

Re: Bug when trying to commit files nested inside a directory

From: leptoon <leptoon_at_gmail.com>
Date: Tue, 7 Dec 2010 01:25:03 -0800 (PST)

Yes, that's exactly what the problem is. I'm having the same problem.
I know what the solution is, I just don't know how to implement it. I
need to include the nested working folder in the working folder of the
parent, and remove the nested folder's working status. In other words,
strip the nested folder's SVN properties completely and add it as a
normal folder to the parent's working folder. Is this possible?

On Dec 3, 3:22 am, Simon Large <simon.tortoise..._at_gmail.com> wrote:
> On 2 December 2010 23:20, Andrew Mainland
> <Mainland_And..._at_solarturbines.com> wrote:
> > Please disregard this email. The problem has something to do with a renamed folder. I am no longer sure what the problem is but I suspect it has already been reported.
> There is almost certainly no problem in subversion/TortoiseSVN,
> otherwise the mailing lists would be groaning under the load of bug
> reports. Most likely the lower level directory has become disconnected
> from its parent in some way, possibly by a rename of the folder
> outside subversion. That subdirectory would then be seen as an
> independent nested working copy, and the original folder name as
> missing. Check for Modifications will show you what is happening.
> Simon
> > Subject: Bug when trying to commit files nested inside a directory
> > Caterpillar: Confidential Green        Retain Until: 01/01/2011
> > This may be a very large bug.
> > I am unable to commit changes if the changed files exist in a directory more than 1 level deep.
> > Say I have a file structure such as the following:
> > trunk\
> > trunk\SomeFile.txt
> > trunk\SomeDir\
> > trunk\SomeDir\FileThatHasChanged.txt
> > From explorer trunk\ will correctly have a red icon indicating that file inside of it has been changed and could be committed. If I right click trunk\ > commit I do not see trunk\SomeDir\FileThatHasChanged.txt in the commit dialoge box. If I navigate inside of trunk and right click SomeDir\ I do see trunk\SomeDir\FileThatHasChanged.txt
> > By "do not see" and "see" I mean the commit dialog box that would allow me to submit a message and select which files I want to commit.  From the trunk\ level's commit dialoge  it would appear that no files have changed.
> > In other words when I right click > commit  Tortise does not seem to be recursively navigating the tree of files so as to report which files have changed so that I can check them for the commit.  This means that I must right click every directory myself.
> > I am on version
> --
> :       ___
> :  oo  // \\      "De Chelonian Mobile"
> : (_,\/ \_/ \     TortoiseSVN
> :   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
> :   /_/   \_\    http://tortoisesvn.net
> ------------------------------------------------------http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMess...
> To unsubscribe from this discussion, e-mail: [users-unsubscr..._at_tortoisesvn.tigris.org].


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-12-07 10:33:51 CET

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