On Thu, Aug 15, 2013 at 2:03 PM, <dlel...@rockwellcollins.com> wrote:
>
>> > We do want to modify in place. Copying back creates an additionalstep
>> > that
>
>> > is already managed quite well by SVN with externals.
>>
>> I've never done that with a file external - where does the commit go?
>
>
> It commits a new revision of what the file external pointed to - pretty
> handy. If you are pegged, it will not automagically update your pegged
> revision (as I'd expect), so unless you are on the HEAD or update your peg
> to what just committed, an update will revert your WC back to the pegged
> version.
I'd actually expect it to be pretty confusing if you had multiple
people committing changes based from different back-rev pegged
references anywhere near the same time frame. Does your external
'notify about new versions' tool help with that? Don't you get
conflicting changes that you'd want branches to help isolate?
--
Les Mikesell
lesmikes...@gmail.com
