Greg Hudson wrote:
> On Thu, 2003-12-11 at 13:12, solo turn wrote:
>
>>how does automerge prevent adding "signed directory content hashes" as a directory property?
>
>
> "Automerge" refers to the server-side merging of directory changes which
> we perform before upon commit. I'll illustrate how it conflicts with
> signing directory content.
>
> Repository is at rev 1000. You and I both have working dirs at rev
> 1000.
>
> I add file foo/bar. I sign the file foo/bar, the directory foo, and the
> root directory, and commit, producing rev 1001.
>
> Without first updating, you add file foo/baz. You sign the file
> foo/baz, the directory foo (which does not contain foo/bar), and the
> root directory, and commit, producing rev 1002. But no one has signed
> the contents of directory foo as it appears in rev 1002; what you signed
> was a version of the directory foo which never actually made revision
> status.
>
> If we didn't have automerge, then your attempt to commit would fail, and
> then you would update, generate correct signatures, and commit. But
> developers would find the system rather less convenient to use.
Even this case could be supported, though at the cost of slightly
greater alteration to subversion's workings. When the server at rev
1001 receives the signed foo/baz commit instead of failing it could
return the signed directory containing foo/bar. The client could check
this signature resign an updated directory listing and return it to the
server.
This would occur without the client actually performing an update of the
WC, i.e. it would change only the protocol not the user experience.
John
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Dec 12 00:22:30 2003