On Tue, 08 Oct 2013 15:46:46 +0200, Richard Hipp <d...@sqlite.org> wrote:
Trunk now escapes just a handful of characters that might cause problems
(\/*?[]). And a comment has been added to the entry box for the "Project
Name" encouraging admins to avoid the use of those special characters.
thanks for fixing this (mostly/completely?).
but I still believe that constructing the name for the zip file (and top
level dir in the archive)
from the (essentially free text) project name is not optimal. of course
one can take care to avoid "problematic characters" but one should not
need to.
e.g., I also use fossil for tracking changes to latex-documents
(manuscripts of journal articles) where project title typically looks like
"a paper addressing something or other". there can be
single/double/back-quotes in this name, parentheses, or whatever, and
several of these characters can cause problems or at least annoyances if
later used in the shell/command line (even if a valid file name results
there might be chars special to the shell). and quoting all these still
makes for difficult to read/handle file names.
I view the download facility mainly as a convenience for "anonymous" to
get hold of the managed files for a certain revision without the need
to clone the whole repo. at least in this use case it sure would suffice
to use a fixed_string+sha1 as the identifier (e.g. `fossil' plus the
sha1). actually I feel it would be easier for the user. so what are the
benefits of using project-name derived (and usually unwieldy) long names
for the generated archives?
--
Using Opera's revolutionary email client: http://www.opera.com/mail/
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
