--On Thursday, August 01, 2002 10:13:29 PM -0400 Shane Hathaway
[EMAIL PROTECTED] wrote:
It's really only a theoretical problem. To store the extra data about
folderish objects, you can save the data in a hidden file called, for
example, .properties. The theoretical problem is that
Shane Hathaway writes:
It's really only a theoretical problem. To store the extra data about
folderish objects, you can save the data in a hidden file called, for
example, .properties. The theoretical problem is that someone might
give an object that name, since it's perfectly legal.
Mehran erfani wrote:
I am a newbie to the zope world and recently started
using zope in our corporate development environment.
One thing that I couldn't find so far is an easy way
to use cvs for revision control for individual
components developed in zope. I understand that zope
has its own
On Thu, 2002-08-01 at 15:04, Shane Hathaway wrote:
There are a few products on zope.org for integrating with CVS. Look
through the downloadable products. I think there are CVSFolder and
ZCVSFile (or something like that), maybe more.
However, most version control tools are difficult to
Gary Poster wrote:
On Thu, 2002-08-01 at 15:04, Shane Hathaway wrote:
There are a few products on zope.org for integrating with CVS. Look
through the downloadable products. I think there are CVSFolder and
ZCVSFile (or something like that), maybe more.
However, most version control tools
On 1 Aug 2002, Gary Poster wrote:
Given a hypothetical folder-like instance called myFLI, we would
presumably want, in CVS (or Subversion, or whatever) a folder named
myFLI containing the children and a file named, to borrow your
example, myFLI.properties.zexp that *only* contains the
