Hi,

I think it's a very nice idea to implement a CVS API. However, would it be possible to commit data to or check data out of a CVS Repository using this API? It would be nice to use a content type as a file, that, if read, takes the data displayed from the CVS Repository, and if edited or created commits the data to a CVS Repository. It would be possible to use the "Parent Item" field of the content as a location for the file in the repository. Something like this could make things like online code development easier.
You can contact me at marufaberlin@gmail.com.

Thanks a lot,

marufaberlin

Comments

jpetso@drupal.org’s picture

jpetso@drupal.org commented
Status: Active » Closed (won't fix)

I would for sure welcome such a feature set, but I think committing (and client-side functionality) is out of scope for this module. Version Control API was always supposed to be a server-side API, and you don't change files server-side. Given, with distributed version control systems, the borders are blurring, but I think the module is both logically separate and already large enough in the code so that it's better not to include client-side functionality. It's really a wholly different beast, and should imho go into a separate API module.

In any case, I won't be coding it. It's a cool idea though, sorry that it won't go into Version Control API.