Bug 63679 - [Operations] Checking out over top of a pruned folder fails
Summary: [Operations] Checking out over top of a pruned folder fails
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: CVS (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows 2000
: P5 normal (vote)
Target Milestone: ---   Edit
Assignee: platform-cvs-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2004-05-24 10:04 EDT by Mike Schrag CLA
Modified: 2019-09-06 16:15 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mike Schrag CLA 2004-05-24 10:04:01 EDT
In 2.1 (and in other CVS clients that I've used), it is a legal operation to
checkout a folder from another location in the repository over top of a folder
that has been pruned.  In 3.0, this results in a failure.

Michael Valenta's response from the mailing list:
Unfortunately, Eclipse CVS needs to keep track of pruned folders for performance
reasons (i.e. without it, synchronize can be extrememly slow if there are a
large number of pruned folders). Therefore, CVS does not support Checkout Into
for these folders. Your options are as follows:

1) Rename or delete the folders in the repository. This may be a problem if the
history for the files that usd to be in these folders is important

2) Checkout the additional contents into a folder of a different name.

3) Define a module in the CVSROOT/modules file that gives you the strucutre you
need and configure the resulting project to not fetch new directories (in the
CVS project properties). 

---

While the performance increase is nice, it would also be nice to be able to opt
for better CVS compatibility over a breaking performance improvement (or perhaps
finding a way to have both would be fine too :) ).
Comment 1 Michael Valenta CLA 2004-05-24 22:09:38 EDT
I think the proper solution would be to support a checkout that configures the 
resulting project to a) not fetch absent directories and b) not remember 
pruned folders. Such a project would not require the sync optimization. No 
time for this in 3.0 though.
Comment 2 Eclipse Webmaster CLA 2019-09-06 16:15:27 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.