X-Git-Url: https://arthur.barton.de/gitweb/?p=bup.git;a=blobdiff_plain;f=DESIGN;h=8c2732dc96fc88ce28f08199cade221b485d3774;hp=e2419186ef057a4b398ce38c969f841445525cf1;hb=fb74d94974aeea5a2c78d3e32afe2aaaaf0d6f61;hpb=1d8470db4ce9bf62d7f8edef579d7590dac555d7

diff --git a/DESIGN b/DESIGN
index e241918..8c2732d 100644
--- a/DESIGN
+++ b/DESIGN
@@ -587,9 +587,10 @@ repository.  What that means is you've chosen not to backup the latest
 version of that file; instead, your new backup set just contains the
 most-recently-known valid version of that file.  This is a good trick if you
 want to do frequent backups of smallish files and infrequent backups of
-large ones (as in 'bup save --smaller').  Each of your backups will be
-"complete," in that they contain all the small files and the large ones, but
-intermediate ones will just contain out-of-date copies of the large files.
+large ones.  Each of your backups will be "complete," in that they contain
+all the small files and the large ones, but intermediate ones will just
+contain out-of-date copies of the large files. Note that this isn't done
+right now, and 'bup save --smaller' doesn't store bigger files _at all_.
 
 A final game we can play with the bupindex involves restoring: when you
 restore a directory from a previous backup, you can update the bupindex