db in _MTN/: -1 db in ~/.monotone: -2 I keep the db for different projects on wildly varying places: - /etc backup: /usr/local/monotone/db (different partition) - versioned work-in-progress: /dir/to/work-in-progress/../work-in-progress.mtn - other projects: /usr/local/src/db
I tend not to host projects in my ~, so keeping the corresponding db in there seems unnatural. And for doing backups or mirrors of certain directories, I don't like to keep the backup in a subdirectory of them, specially if it's something like /etc. nicolás Matthew Gregan wrote: > I really don't like the idea of the repository being stored in _MTN/ like > this. > > Using ~/.monotone is quite a bit better, but it's not ideal. It would mean > that the repository would end up in %APPDATA%/monotone on Windows, which is > part of the user's profile that might be part of a roaming profile in a > domain, which would mean the repository would be copied back and forth each > time they logged in to a machine. > > I'd prefer to have clone require a --db argument be supplied. _______________________________________________ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
