Re: checkin-set

This is a multipart message in MIME format.
--=_alternative 0070DD308525714E_=
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

Werner Donn=E9 <[email protected]> wrote on 04/12/2006 03:21:44 PM:

> >> each branch could be checked out if there is a workspace,
> >> which has a VCR, that is linked to the first version of that branch.
> >=20
> > Not sure what you mean by "linking the VCR to the first version of=20
that
> > branch".

> I meant a workspace with a VCR that was created with the first version
> of the branch/activity.

In general, there would not be (and would not need to be) such a=20
workspace.

> > You indicate what branch/activity you are working on by setting the
> > DAV:current-activity of your workpspace to reference that=20
branch/activity.

> I think this is the clue. If the current activity of a workspace is
> changed, can this affect the checked-in version of a VCR? Is the system
> allowed to set it to the most recent version within the activity if
> such a version exists?

You can do this, but you use the MERGE method (see section 13.12 in=20
RFC-3253).
Changing the DAV:current-activity of the workspace has no effect
on the checked-in version of any VCR in the workspace.=20
=20
> > When you checkout a VCR, you checkout the version of that VCR
> > that is in that configuration, and if you want some other version to
> > appear in that configuration, you perform an UPDATE to make that
> > version appear in that workspace.

> Do I understand it correctly then that if a user wants to check out on a
> branch/activity within a version history he has to "import" the last=20
version
> in that activity by making sure there is a VCR in his workspace that has
> its checked-in version set to it? Possibly the user has to create a VCR=20
first
> in his workspace using that version.

Yes.

> If that is true, and assuming collections are supported, the user has=20
the
> flexibility to create his own "directory tree" in his workspace with all =

the
> items he is working on.

He could do that, but it would be more useful for the collections to be=20
under
baseline control, so that the user UPDATEs his workspace with a baseline,
which pulls in a consistent configuration of all of these items and of the
collections that contain them (so that the namespace of the files items is
under version control as well).

> On the other hand he always has to do this "import"
> action and manage this "directory tree". Would it be allowed to generate
> VCRs automatically when a workspace is created? For example, VCR /a/b/c=20
would
> lead to /ws/myws/a/b/c.

Yes, that is what baselines and BASELINE-CONTROL of collections provides.

Cheers,
Geoff



--=_alternative 0070DD308525714E_=
Content-Type: text/html; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable


<br><tt><font size=3D2>Werner Donn=E9 &lt;[email protected]&gt; wrote on 0=
4/12/2006
03:21:44 PM:<br>
<br>
&gt; &gt;&gt; each branch could be checked out if there is a workspace,<br>
&gt; &gt;&gt; which has a VCR, that is linked to the first version of that
branch.<br>
&gt; &gt; <br>
&gt; &gt; Not sure what you mean by &quot;linking the VCR to the first
version of that<br>
&gt; &gt; branch&quot;.<br>
<br>
&gt; I meant a workspace with a VCR that was created with the first version=
<br>
&gt; of the branch/activity.</font></tt>
<br>
<br><tt><font size=3D2>In general, there would not be (and would not need
to be) such a workspace.<br>
<br>
&gt; &gt; You indicate what branch/activity you are working on by setting
the<br>
&gt; &gt; DAV:current-activity of your workpspace to reference that branch/=
activity.<br>
<br>
&gt; I think this is the clue. If the current activity of a workspace is<br>
&gt; changed, can this affect the checked-in version of a VCR? Is the syste=
m<br>
&gt; allowed to set it to the most recent version within the activity if<br>
&gt; such a version exists?</font></tt>
<br>
<br><tt><font size=3D2>You can do this, but you use the MERGE method (see
section 13.12 in RFC-3253).</font></tt>
<br><tt><font size=3D2>Changing the DAV:current-activity of the workspace
has no effect</font></tt>
<br><tt><font size=3D2>on the checked-in version of any VCR in the workspac=
e.
&nbsp;</font></tt>
<br><tt><font size=3D2>&nbsp;<br>
&gt; &gt; When you checkout a VCR, you checkout the version of that VCR<br>
&gt; &gt; that is in that configuration, and if you want some other version
to<br>
&gt; &gt; appear in that configuration, you perform an UPDATE to make that<=
/font></tt>
<br><tt><font size=3D2>&gt; &gt; version appear in that workspace.<br>
<br>
&gt; Do I understand it correctly then that if a user wants to check out
on a<br>
&gt; branch/activity within a version history he has to &quot;import&quot;
the last version<br>
&gt; in that activity by making sure there is a VCR in his workspace that
has<br>
&gt; its checked-in version set to it? Possibly the user has to create
a VCR first<br>
&gt; in his workspace using that version.</font></tt>
<br>
<br><tt><font size=3D2>Yes.<br>
<br>
&gt; If that is true, and assuming collections are supported, the user
has the<br>
&gt; flexibility to create his own &quot;directory tree&quot; in his worksp=
ace
with all the<br>
&gt; items he is working on.</font></tt>
<br>
<br><tt><font size=3D2>He could do that, but it would be more useful for
the collections to be under</font></tt>
<br><tt><font size=3D2>baseline control, so that the user UPDATEs his works=
pace
with a baseline,</font></tt>
<br><tt><font size=3D2>which pulls in a consistent configuration of all of
these items and of the</font></tt>
<br><tt><font size=3D2>collections that contain them (so that the namespace
of the files items is</font></tt>
<br><tt><font size=3D2>under version control as well).</font></tt>
<br>
<br><tt><font size=3D2>&gt; On the other hand he always has to do this &quo=
t;import&quot;<br>
&gt; action and manage this &quot;directory tree&quot;. Would it be allowed
to generate<br>
&gt; VCRs automatically when a workspace is created? For example, VCR /a/b/c
would<br>
&gt; lead to /ws/myws/a/b/c.</font></tt>
<br>
<br><tt><font size=3D2>Yes, that is what baselines and BASELINE-CONTROL of
collections provides.</font></tt>
<br>
<br><tt><font size=3D2>Cheers,</font></tt>
<br><tt><font size=3D2>Geoff</font></tt>
<br><tt><font size=3D2><br>
<br>
</font></tt>
--=_alternative 0070DD308525714E_=--