Bug 89180 - [Repo View] Add module to those listed under repo root
Summary: [Repo View] Add module to those listed under repo root
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: CVS (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P5 enhancement (vote)
Target Milestone: ---   Edit
Assignee: platform-cvs-inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2005-03-26 22:51 EST by Philippe Ombredanne CLA
Modified: 2019-09-04 01:58 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Philippe Ombredanne CLA 2005-03-26 22:51:37 EST 
It is impossible to checkout a module or submodule from a CVS repository from
the CVS repository view if the CVS server does list the modules.
An example is the cvs.tigris.org repository. The root is /cvs but modules are
not listed.

The workaround is to use the CVS project wizard.

However, it would be nice to have the possibility, when adding a CVS repository,
to be able to add a module name or even sub-module name, but not padding it to
the CVS root.

TortoiseCVS works like that, and also goes further by trying to get a list from
modules from viewCVS, or other CVS web interfaces, with URLs inferred from the
cvs server you are trying to connect to, and when the server does nmot list modules.
Comment 1 Michael Valenta CLA 2005-03-28 12:10:18 EST 
That was the intent of the CVS Project Checkout Wizard. What you describe is a 
more deluxe solution but we do not have the manpower to address it.
Comment 2 Lars Vogel CLA 2019-09-04 01:58:00 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 and remove the stalebug whiteboard tag. 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.

--