For the (not yet existing) release node integration and slightly more advanced repository browsing, we want CVS repositories to be navigable with regards to branches and tags, in other words, the caller should be able to use versioncontrol_get_parallel_items() to get all branches and tags of a given item. Which means the CVS backend should implement versioncontrol_cvs_get_parallel_items().

As precondition for release node integration, this is also a required in order to get Version Control API running on drupal.org.

Comments

jpetso’s picture

jpetso commented

Note: this should be doable with cvslib_log(), as that function parses the branches and tags of the file (or each file in a directory, if the source item is a directory). Running cvslib_log() recursively on the root directory might not be the best idea though... maybe there's some other way to retrieve the possible branches and tags for a directory.

jpetso’s picture

jpetso commented
Assigned: Unassigned » jpetso

Assigning to myself, I really want to get this done soon.

jpetso’s picture

jpetso commented
Version: 5.x-2.0-rc2 » 6.x-1.0-beta2
Status: Active » Fixed

Implemented in commit #186428.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.