Re: Can't commit external subprojects to same repository in one go

The commit command only ever works on one repository at a time. So no, you
can not commit every external in one go, you need to commit them separately.

On Jan 5, 2008 4:37 AM, Scott Barnes <sbarnes_tsvn_at_atomsmith.net> wrote:

> Hi,
>
> I am having problems committing changes to an svn:external subproject
> using TortoiseSVN v1.4.6. When I commit from the top level of the
> working copy, I can see modifications in the subproject. However,
> even though the subproject files are in the same repository, the
> subproject changes are not actually committed to the server.
>
> According to section B.6.1 in the help file, I should be able to
> commit all my main project and subproject changes in a single
> operation. Indeed, the commit dialog shows every indication that the
> commit should work. The commit results window does not show any
> errors; the subproject(s) just get skipped over.
>
> Here are some details about my directory structure:
>
> toplevel
> |
> --- app
> |
> --- common
> |
> ---- component
>
> "toplevel" is a checkout from http://svn.server:8080/repos1/project/trunk
> "common/component" is an svn:external to
> http://svn.server:8080/repos1/common/component
>
> When checking for modifications at the top level, "common/component"
> shows up as Nested. The nested indication seems misleading, since the
> working copy was created with a single checkout, not nested checkouts.
>
> Thanks,
> Scott
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
> For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
>
>

-- 
Lasse Vågsæther Karlsen
mailto:lasse_at_vkarlsen.no
http://presentationmode.blogspot.com/
PGP KeyID: 0x01B3972E