Is there some documentation of the rules that a *tailor* Changeset must follow?
Having a good knowledge of the aegis changeset model but zero of other systems I need some clarification. The following holds for aegis: * file operations: create, modify, remove, rename, insulate, transparent create, modify, remove and rename has a natural mapping in the tailor changeset model. I don't see a mapping for insulate and transparent. Insulate is not a problem since it's a valid operation only for uncommitted changeset, while I don't know if other system has an operation similar to transparent (see aemt(1)). * for each changeset only 1 operation is allowed on a file. Since I've seen some system (i.e. darcs) permits more than one action per file on a single changeset, this rule means that the aegis target backend must collapse operation sequences. Under aegis, renaming a file and modifying its content result in a single operation: rename. Should the (not yet written) source backend split it in a REN followed by an UPD? How a target backend should use the old_revision, new_revision and status member of a ChangesetEntry? Expects more questions :-) -- Walter Franzini http://aegis.stepbuild.org/ PGP Public key ID: 1024D/CB3FEB43 Key fingerprint : FA26 C33B CAFF 7848 EFEB 7327 96AA 2D57 CB3F EB43 Key server : http://www.keyserver.net
pgpl0ycGYcLHI.pgp
Description: PGP signature
_______________________________________________ Tailor mailing list [email protected] http://lists.zooko.com/mailman/listinfo/tailor
