SteveKing <email@example.com> wrote:
> Stefan.Fuhrmann@etas.de wrote:
> > C:\develop>svn propget svn:externals p2
> > ..\p1 file:///C:/temp/t/p1/trunk
> Are p1 and p2 pointing to the same repository? Or are they from
> different repositories?
They are in the same repository.
> If they're from the same repository, then you _could_ commit changes in
> both with one commit.
Nope, I can't.
A collegue of mine that originally stumbled accross this problem
told me that it is even worse; even "ordinary" externals as sub-
folders will be ignored (all within the same repository):
C:\temp\x>svn propget svn:externals p2
C:\temp\x>svn st p1
Performing status on external item at 'p2\sub'
C:\temp\x>svn ci p2 -m "this will not succeed"
> I guess you're thinking about a TSVN workaround, most likely because I'm
> usually faster doing things ;)
Mindreading works .. cool ;)
> But you can do the workaround yourself: just uncheck at least one file
> from being committed, then TSVN will do a non-recursive commit and
> therefore commit the externals too (_if_ they're from the same repo).
Thanks for that hint. It seems to work.
> > Hope that doesn't turn out to be overly complicated.
> Not complicated, but almost impossible. Sorry.
> Sure, there may be ways to really work around this, but this would
> require non-recursive commits which TSVN already does if not all items
> shown in the commit dialog are to be committed. But non-recursive
> commits can cause problems with Subversion, especially if you try a
> non-recursive commit on deleted/moved/renamed folders...
> So a workaround would work in some situations, but break in others. Now
> guess what I'm (not) doing? ;)
I see your point. But since your proposed workaround would be
acceptable for the users in my company, it would be very nice
to have an additional checkbox that deliberately forces the
Thanks in advance,
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Tue Aug 3 15:40:34 2004