Re: How to change paths on an external file without a full update --depth infinity?

> >
> > 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?

Yes, its obvious to users when they are not on the latest revision of the
file, but they c/would still go through a merge process if need be.

Its actually very straight-forward as we intentionally focused on
targeting non-CM-guru folks.
Received on 2013-08-15 23:04:12 CEST