No, you're not missing anything. Fossil has some strict rules about filenames. In fossil source file.c, line 425 you can see:
/* ** Return true if the filename given is a valid filename for ** a file in a repository. Valid filenames follow all of the ** following rules: ** ** * Does not begin with "/" ** * Does not contain any path element named "." or ".." ** * Does not contain any of these characters in the path: "\*[]?" ** * Does not end with "/". ** * Does not contain two or more "/" characters in a row. ** * Contains at least one character */ On Mon, Apr 2, 2012 at 20:41, Sander Reiche <sander.rei...@gmail.com> wrote: > Hi people, > > Maybe I'm missing something like a magic argument to 'fossil add', but > this is not an error I'd like to see on a source control program > supported on a UNIX platform :) > > fossil: filename contains illegal characters: > lite2/local/MACH/386/sys/standi386at/binaries/bin/[ > > I guess it's the '[', but come on... > > re, > > Sander Reiche > the Netherlands > > -- > ~ UNIX is basically a simple operating system, > but you have to be a genius to understand its simplicity. ~ dmr > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- Benoit Mortgat _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users