W3C home > Mailing lists > Public > ietf-dav-versioning@w3.org > October to December 2000

Re: Working collections

From: Jim Amsden <jamsden@us.ibm.com>
Date: Tue, 12 Dec 2000 22:32:00 -0500
To: ietf-dav-versioning@w3.org
Message-ID: <OF87D4EDB3.89B39150-ON852569B4.0013556A@raleigh.ibm.com>
What about all those .o files (derived files) that happen to be in the same
workspace, and should never be versioned?

   From: Greg Stein <gstein@lyra.org>

   On Wed, Nov 22, 2000 at 03:39:25PM -0500, Geoffrey M. Clemm wrote:
   > ...
   > I have what I believe is a simpler proposal.  You can create as many
   > non-versioned resources as you want in a working collection.  When
   > you checkin a working collection, all non-versioned resources are put
   > under version control, and are replaced by their (newly created)
   > version history resource.  The "put under version control" works
   > leafs up, so you can create trees of non-versioned resources inside
   > of a working collection before checking it in.  The working collection
   > is deleted on checkin, as a working resource is, but all your work is
   > saved in the standard form of versions and version histories.
   > ...
   > How's all this sound?

   Sounds terrific, and it shouldn't be too hard to model code-wise.

Excellent.  I'll write up this working collection proposal up for
general review.

Received on Wednesday, 13 December 2000 10:55:59 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:55:46 UTC