W3C home > Mailing lists > Public > ietf-dav-versioning@w3.org > April to June 2002

Re: question about Version-Control

From: Tim Ellison <Tim_Ellison@uk.ibm.com>
Date: Wed, 5 Jun 2002 11:20:38 +0100
To: "IETF DAV" <ietf-dav-versioning@w3.org>
Message-ID: <OF85A683A3.C002DC40-ON80256BCF.00381AE4@portsmouth.uk.ibm.com>

"Elodie Tasia" <e.tasia@ever-team.com> wrote:

> > A version is created as a copy because the version-controlled resource
> > be checked out and modified.  The version remains as an immutable copy
> > the inital state of the VERSION-CONTROL'led resource.
> Hmm, I compared the version-controlled resource to a sort of 'root', and
> thought it was immutable... I made a mistake.

A version-controlled resource is a resource with defined DeltaV behavior,
notably CHECKOUT to make it mutable and CHECKIN to capture it's state as a
version resource and make it immutable.  RFC3253 has lots to say about
version-controlled resources.

> But why is it possible to modify it, if I can create descendants with the
> first version of the history ?

You can either modify the checked-out version-controlled resource, or a
working resource of a version to create a descendant depending upon whether
the server or client is maintaining the 'workspace' or work in progress.
See section 2.1 for an overview of the differences.

Received on Wednesday, 5 June 2002 06:20:59 UTC

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