Re: A question about branching, merging
Geoffrey M. Clemm (geoffrey.clemm@rational.com)
Wed, 8 Dec 1999 09:09:38 -0500
Date: Wed, 8 Dec 1999 09:09:38 -0500
Message-Id: <9912081409.AA01947@tantalum>
From: "Geoffrey M. Clemm" <geoffrey.clemm@rational.com>
To: ietf-dav-versioning@w3.org
In-Reply-To: <9912080530.AA01770@tantalum> (geoffrey.clemm@rational.com)
Subject: Re: A question about branching, merging
I just added to the spec this more detailed description of how
merging is performed using the protocol. In the process of
doing so, the assymetry of picking one merge contributor to
be the "predecessor" and the rest as "merge-predecessors" became
evident.
I know there was one advocate during the breakout in Washington
of keeping these properties distinct, but I remain unconvinced.
So I'd like to hash this out on the mailing list so that we
can either convince ourselves that this distinction is important,
or convince ourselves that the spec. should be simplified by replacing
the four properties:
DAV:predecessor, DAV:successors, DAV:merge-predecessors, DAV:merge-sucessors
with the two properties:
DAV:predecessors, DAV:successors.
Note: I will interpret silence to mean consent that we simplify (:-).
Cheers,
Geoff