On Tue, Apr 27, 2010 at 4:42 PM, Timothy Brownawell <tbrow...@prjek.net> wrote: > > Is the occasional backslash really that bad? '%' conflicts with urlencoding > (and '*' would only actually glob things if you have some really weirdly > named files), and '?' is probably necessary for file/ssh sync.
I think it's more important to avoid characters that are meaningful in URLs (*especially* %) than to avoid characters that are meaningful to the shell. People expect to have to quote URLs. Also, I don't like / as a separator when it's not traversing a directory-like hierarchy. So, how about this? protocol://u...@server.host.name/path/to/database?include,include,-exclude,-exclude should work equally well for mtn (with usher), ssh, and file. Without usher, you just leave out the /path part. (Also, ~ in the path part should absolutely have the 'go to home directory' semantic.) zw _______________________________________________ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
