You are correct. I tried manually "Team -> Add" of the file and then
"Replace with" on the containing directory and all it did was change
the status of that file back to "un-versioned". This behavior is
really only problematic when you have added a bunch of files and
realize and that you want to switch version or possibly roll the
entire project to the respository's latest. Is there anything I can
do except manually remove all these new files?
Bradley
On May 12, 2006, at 3:11 PM, Mark Phippard wrote:
> Bradley Wagner <bradley.wagner@hannonhill.com> wrote on 05/12/2006
> 03:07:41 PM:
>
>> One side effect I've seen from files not being auto-added and this is
>> noticeably different than CVS is that if I create a new file and then
>> "Replace with" latest from the repository that unversioned file is
>> still in my workspace. CVS, in contrast, would literally replace the
>> entire contents of that folder with what was in the repository. I'm
>> not sure that would be fixed by having these new files already marked
>> as versioned but I can test it.
>
> I suspect it wouldn't fix it. Subversion is very conservative about
> destroying data. That is why revert of an added file does not
> provide an
> option to delete the file. In your example, I think the file would
> remain.
>
> Mark
>
>
> ______________________________________________________________________
> _______
> Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by
> IBM Email Security Management Services powered by MessageLabs.
> ______________________________________________________________________
> _______
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
> For additional commands, e-mail: users-help@subclipse.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Fri May 12 21:16:53 2006