Checkout existing branch to established workspace (.moved)

[Bulgrien, Kevin]

> I believe that in most cases, using the versions from the branch that
> were all committed together is more likely to produce a set of files
> that work with each other.  I believe that in most cases, using a mix
> of on-disk versions and branch version is more likely to break the
> workspace, because the on-disk versions won't match the branch
> versions' expectations.

Wait a minute... If it didn't move files that were different, how would
it create a "mixed" set of files?  I should think that the existing
buildability state would still be preserved and that any new files
Probably Would usually not impact the build.  This may go back
to differences of opinion as to whether my or your files are more
important.  I guess if you are a repo owner you might think your state
is more important, but don't people tend to think their own state is
more important?

Am I missing something?

Kevin Bulgrien

This message and/or attachments may include information subject to GD Corporate Policy 07-105 and is intended to be accessed only by authorized personnel of General Dynamics and approved service providers.  Use, storage and transmission are governed by General Dynamics and its policies. Contractual restrictions apply to third parties.  Recipients should refer to the policies or contract to determine proper handling.  Unauthorized review, use, disclosure or distribution is prohibited.  If you are not an intended recipient, please contact the sender and destroy all copies of the original message.