> On 17/03/2009, John Doe <wfry6f..._at_sneakemail.com> wrote:
>
> > I have some externals in a project where the external is a fixed
> > revision (using 'folder -rxxxx repo\path' etc).
> > To my understanding, once checked-out, if one of the files from the
> > external are edited, then the folder committed, the external itself will be changed.
> > (in a newer revision).
> > I would like to prevent this happening (essentially making files
> > that are checked out because they are part of an external, read-only
> > & not committable).
> > Is there an easy way to accomplish this?
> IIRC changes to an external that is fixed at a specific revision
> cannot be committed (because that part of the working copy has not
> been 'updated' to HEAD prior to the commit).
> Regards,
> Jean-Marc
I would have expected that it wouldnt allow a commit of the 'revision locked' external.
- But it does, I have made a dummy repository and tested it.
It is very confusing, as when you change the file from inside the external then commit it, that file in the head is changed, but the file in the external itself goes back to what it was before (as it must).
Im guessing this is unintended operation - Bugfix please?
In the meantime is there any easy way to prevent this situation - eg any way to lock the files in the external but not lock the original files in the head?
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=1351953
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-03-19 07:07:01 CET