"Andy Jones" <[EMAIL PROTECTED]> writes: [...]
> 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. > > Eeek. That isn't good. Why is that so bad? syncing databases is a normal part of working with monotone. > I would have thought that this was a pretty likely use case, if you > compare with how CVS or Subversion is used. OK, with CVS you can probably get away with removing things from the repository. I'm not entirely sure---maybe CVSROOT/history has stuff, and you'd might want to edit CVSROOT/modules. How would you do this with subversion? Surely you need to do svnadmin dump, then filter, then svnadmin load into a new repository? That's *much* more of a problem than using sync in monotone to a new database, isn't it? _______________________________________________ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
