Emile Snyder <[EMAIL PROTECTED]> writes: > On Thu, 2005-05-12 at 06:39, Bruno Hertz wrote: >> What we are talking about here is situations where files under >> revision control are sparse in a directory tree. As an example, >> consider putting your home directory under revision control for files >> like ~/.profile or ~/.emacs. In such a scenario, commands like list > > Given that monotone is about versioning trees of files, this seems kinda > like twisting it out of it's groove to me. Is there a problem with just > having a myconfigs project, and symlinking; eg. ~/.emacs to > ~/myconfigs-workingdir/.emacs ? Seems cleaner.
Well, putting /etc under revision control was a recent svk usage example in a Debian news letter, and it makes sense. The same applies for scenarios like various configuration files in home directories and dot subdirs, like .monotone/ or whatever. And no, I think it's not a good option to 'set up' your home dir for revision control, symlinking all kinds of stuff from various locations. That's the neatness of monotone after all, that it's actually not concerned with directory trees. It's concerned with files, sitting somewhere in a tree. What makes it look like being concerned with trees is the UI only, e.g. the recursiveness we've been talking about, but this is actually just an interpretation, and limitation, of it's capabilities. Regards, Bruno. _______________________________________________ Monotone-devel mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/monotone-devel
