[development] Drupal's CVS policies... including 'foriegn' code in TinyMCE module?

Yuval Hager yuval at avramzon.net
Wed May 23 08:44:44 UTC 2007

> Hm, seems that this approach is still not quite usable.
> Let's have another try:
> Each project release gets an additional "External library tarball" upload
> field, which takes either .tar.gz or .tar.bz2 files, and on creating the
> release this file is unpacked into the module's root folder.
> After creating the release, the file can not be changed anymore.

I just posted a comment on this about CVS internal ability to manage third 
party code - vendor branches.


More information about the development mailing list