-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Andy Jones wrote: > Or, is this a "best practice" thing? Should I have pulled the > branch into a new database? Mhh.. in fact if you are in the "I'm not sure I want it forever" area, you probably should better import it in a new DB, yes. To remove it from the DB you have to use the scary command: mtn db kill_branch_certs_locally BRANCH-NAME which deletes from the DB the certificates of that branch, though it doesn't remove file contents (because other branches could be using them: if a file is the same in content even if in different branches, directory or filenames, they are stored only once).
In order to get rid of the extra file size you'd have to create a new DB and locally sync the branches you're interested in into the new DB, and then drop the old one. - -- Lapo Luchini [EMAIL PROTECTED] (OpenPGP & X.509) www.lapo.it (Jabber, ICQ, MSN) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.1 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQIcBAEBAgAGBQJE7KPmAAoJELBiMTth2oCDc3MP/0RaFyTlxbNT6yO2YYUptc4S izXXagGkgyk289zWvr9oauVcRnqKgeV7aAVdIVV5GJeAjW0cvnC35xIzrIuR0Zww p0I9tBFmO2YOJlgZK8Sjk4zsqmXyiJ3pfvKG1mdQR34P0/7BxgOIxk6e+0JNSxoN rQ/6LASFxX9sTyG1O9+T2hPN8I3uPmjyGtAMOn4EafVkRKke4RTXuWBFIIDz1I8J GrY46odcVt8bVpkTx+BDusD3kcP5aWaGKilGqk02ac9ttFueBFAXykc2/q+CAgGC vSdfwQIzlV/eHD3HQnq4hPtmIlmdZrj7FsySPT8tcsJKn6HzgKtcukV+imdR1+gw OiyT48kQJWOszJeELp3G1M3AlCzW8D9rkaJsY1l79UHszW3lOCYbP+qTRI05R20N GHGno3oQbpi6Y1N4KoryBVXL++hDmeSkS52Lqp7GsqATAYwk36zfM9F4ng2Fvwpf zUpOTGhwCpKAVASlb7ooAOrNUrsNWe+AYjT3MpKeSQpMPvVM5CFM2fmsNCyxT7xZ Mmk04lmCzlX9Odp0eK0RujeB7qC008aODxiNuwn+s5C5EhyKz3JnxMjPfSKvdjIC qadVx2Sm/0aEHv3lLPb+ZhmFMiIGufziZFwNX0AWfBgyqhiNuZLCxNfcFMsxdTm2 hSLypK9mI7gjqyqJhJYt =xxEC -----END PGP SIGNATURE----- _______________________________________________ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
