About http://bugs.bugseverywhere.org/, I just pulled three bugs via xml export/import (the two we just dealt with as well as bea/c3f (cjb) / bea/64c (wtk)). There should be a better way to do this...
It's actually easy to poll for differences: $ be --repo http://bugs.bugseverywhere.org/ diff 'HEAD@{3 months ago}' New bugs: bea/b39:om: created-tags break import-xml bea/5a1:om: xml import of new bugs is broken bea/c3f:om: Set default user paths according to PEP370 $ be diff 'HEAD@{3 months ago}' New bugs: bea/64c:om: Set default user paths according to PEP370 bea/35a:fm: created-tags break import-xml bea/4bc:fm: xml import of new bugs is broken Modified bugs: bea/773:ft: 1.0 Changed bug settings: status: open -> fixed It's also easy to import missing bugs: $ be --repo http://bugs.bugseverywhere.org/ show --xml /5a1 | be import-xml - But it's annoying to have to run a diff to check for new activity and then have the UUIDS change on import/export. I think we should have a '--preserve-uuids' option in import-xml that avoids the whole alt-id business for user-verified XML. We could also add an email-pinger to send change notifications, along the lines of be-handle-mail's subscriber notification. That way bugs.bugseverywhere.org could email me directly and we wouldn't have to poll for changes. Thoughts? -- This email may be signed or encrypted with GPG (http://www.gnupg.org). The GPG signature (if present) will be attached as 'signature.asc'. For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy My public key is at http://www.physics.drexel.edu/~wking/pubkey.txt
pgpn8qYmGjQ6l.pgp
Description: PGP signature
_______________________________________________ Be-devel mailing list [email protected] http://void.printf.net/cgi-bin/mailman/listinfo/be-devel
