# # patch "ChangeLog" # from [dc27c6d632887b760d6b6dcec5d61936d4020da4] # to [4f5d38c23ff44435d5657bcdcc9ccb93f7976e09] # # patch "monotone.texi" # from [f5c2772132d6e3b05043260e09e66fd945e2ee20] # to [e4a42059771b12538e575453621b24cc20ddf2ad] # --- ChangeLog +++ ChangeLog @@ -1,5 +1,10 @@ 2005-06-07 Nathaniel Smith + * monotone.texi (Storage and workflow): Attempt to thwart some + common misconceptions. + +2005-06-07 Nathaniel Smith + * netsync.cc (rebuild_merkle_trees): Add a comment describing how this code should work (and why it currently doesn't quite). --- monotone.texi +++ monotone.texi @@ -667,12 +667,14 @@ A @dfn{database} is a single, regular file. You can copy or back it up using standard methods. Typically you keep a database in your home -directory. Databases are portable between different machine types. If -a database grows too big, you may choose to remove information from -it. You can have multiple databases and divide your work between them, -or keep everything in a single database if you prefer. You can dump -portions of your database out as text, and read them back into other -databases, or send them to your friends. +directory. Databases are portable between different machine types. You +can have multiple databases and divide your work between them, or keep +everything in a single database if you prefer. You can dump portions of +your database out as text, and read them back into other databases, or +send them to your friends. Underneath, databases are accessed using a +standard, robust data manager, which makes using even very large +databases efficient. In dire emergencies, you can directly examine and +manipulate a database using a simple SQL interface. A database contains many files, manifests, revisions, and certificates, some of which are not immediately of interest, some of