I remember having tried to fossilize files in the Ms Office 2007 formats; the docx, xlsx, etc. formats are merely zips containing mainly XML files. The root file is called [Content-Types].xml
Even if it is not sane to include such characters in file names, those characters happen to exist. On Tue, Mar 6, 2012 at 19:24, Leo Razoumov <slonik...@gmail.com> wrote: > On Tue, Mar 6, 2012 at 10:14, Ștefan Fulea <fulea.ste...@gmail.com> wrote: > > > > So I'm ending up in the same questions - why does it have to be an > > blocking error and not a simple warning? The problem that makes sense > > reporting as an error might be at information retrieval, and that's > > if, only if, it will be the case (most likely not). For now, the > > entire architectural decision appears to me like trying to cure a > > disease by shooting the patient dead! In it's current state, Fossil is > > not a keeper, sorry. > > After giving it a second thought I am fine with avoiding [*^] > characters as part of filenames for two reasons: > (1) fossil glob patterns use [*^] for special purposes > (2) [abc123] syntax designates an artifact's SHA1 hash prefix > > --Leo-- > > P.S. Each SCM system has its own arbitrary limitations. In GIT, for > example, :~^ cannot be used in tag/branch names. > _______________________________________________ > 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
