Hi, I separated the less controversial automate extensions of cvssync3 into the branch net.venge.monotone.cvssync.candidates .
Can you take a look whether these are fitting into mainline? (Documentation is added, a ChangeLog isn't yet) Namely they are: db_get domain varname db_set domain varname value (like mtn db get/set) cert name value (like mtn cert) put_file [base-id] contents put_revision changeset The last three commands are needed for workspace-less commits (committing directly into a database without setting up a workspace). This might be interesting to other frontends (e.g. web based), too. Yet unproposed extensions for cvssync2/3 include: find_newest_sync domain [branch] get_sync_info revision domain put_sync_info revision domain value but I would like to merge the uncontroversial ones first. Christof PS: cvssync1 used certificates to store the information cvssync2 used a special file (and certificates on push) cvssync3 uses file attributes (and certificates)
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
