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

Re: bugreport: commit of two 'external' directories fails

From: Erwin Coumans <erwin.coumans_at_gmail.com>
Date: Fri, 31 Oct 2008 14:29:54 -0700 (PDT)

I tried to reproduce it, and it seems to only fail in a second
checkout, with a new copy of the repository (repoA and its
svn::externals repoB).

So in the original location, the commit works fine, and in the second
checked-out version it doesn't.

>>* unchecked entries are in the commit dialog
>>* files were changed while the commit dialog was open

There are certainly no unchecked entries, and no changed files while
the dialog was open.

Can you create testRepoA and testRepoB, with testRepoA having two
separate svn::externals pointing to folders in repoB

repoA/folderA/externalFolderB0/testFileB0 <- svn::externals
externalFolderB0 -> repoB/somepath/otherFolder0
repoA/folderA/externalFolderB1/testFileB1 <- svn::externals
externalFolderB1 -> repoB/somepath/otherFolder1

Then, do a fresh checkout of this testRepoA in a different location,
and try to modify testFileB0 and testFileB1, and try to select both
repoA/folderA/externalFolderB0 and repoA/folderA/externalFolderB1 for
a commit.
This fails here.
Hope you can reproduce this,

On Oct 31, 1:55pm, "Stefan Kng" <tortoise..._at_gmail.com> wrote:
> On Fri, Oct 31, 2008 at 21:49, Stefan Kng <tortoise..._at_gmail.com> wrote:
> > Erwin Coumans wrote:
> >> It seems a TSVN specific issue, because command-line svn just works
> >> fine:
> >> svn commit external1 external2
> >> results in a single commit:
> >>http://code.google.com/p/bullet/source/detail?r=1437
> >> What svn command(s) does TSVN send when you select multiple externals
> >> directories and commit?
> > Just tried this with my test repo: when I select two externals from the
> > same repo and commit the changes, it works as expected.
> > TSVN commits the two selected externals the same as the mentioned svn
> > command. The only thing that could be different is that TSVN could pass
> > the --non-recursive flag with the commit. But that would only happen if
> > while you had the commit dialog open a file inside those external
> > folders was touched (i.e., had is last-modified time changed).
> > Or if you have entries in the commit dialog which were not selected.
> More info: after some more testing I can tell you that this only
> happens if TSVN commits the changes non-recursively.
> And as mentioned in my last mail, that only happens if:
> * unchecked entries are in the commit dialog
> * files were changed while the commit dialog was open (hit F5 to
> refresh before you click on OK to 'clear' those monitored changes and
> allow a recursive commit).
> Stefan
> --
> ___
> oo // \\ "De Chelonian Mobile"
> (_,\/ \_/ \ TortoiseSVN
> \ \_/_\_/> The coolest Interface to (Sub)Version Control
> /_/ \_\ http://tortoisesvn.net

To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-10-31 22:36:08 CET

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

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