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

RE: externals no longer "read only"?

From: Erik Hemdal <erik_at_comprehensivepower.com>
Date: Tue, 29 Jul 2008 16:38:31 -0400

> -----Original Message-----
> From: Keith Moore [mailto:Keith.Moore_at_securency.com]
> Sent: Monday, July 28, 2008 6:51 PM
> To: 'Subversion'
> Subject: RE: externals no longer "read only"?
> . . . .
> However,
> when you do a commit on the main working copy it doesn't
> traverse into the externals directory's, i.e. it doesn't
> commit any changes.

I tested this and you are completely correct. But I discovered that if you
commit specifically in the directory that you "pulled", that you can still
commit changes. If my svn:externals property is set up to pull in a tag
from another repository, then this will let me modify a tag. I found this
to be true even if I have a pre-commit hook in the external repository.

I set a specific rev in the external definition that I wanted. If I pulled
again or did an svn update, then I found I can always get back to the right
revision for the external code. But the underlying tag in the expternal
repository was still modified.

We use TortoiseSVN, and it will warn you if it thinks you're trying to
commit to a tag. But I found you can go past that warning dialog and go
change your tag. I didn't expect that to happen.

I don't know if this is caused by a mistake I made, if my pre-commit script
isn't robust enough, or if this is just the way that externals work.


To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-07-29 22:38:01 CEST

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

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