Matt Welland<estifo...@gmail.com> wrote:
IMHO a more viable philosophy is to use documentation and methodology
to make seamless interoperability between Windows and Unix/Linux
possible for teams that need it. Otherwise where possible and where
the code cost is not too high, independently make fossil work
perfectly on Unix and perfectly on Windows.
Agree.
Out of curiosity, is there someone that's already followed Richard's
advice and created their own branch of fossil, disabling just those
three lines? If so, do they often run into trouble with the mentioned
files?
I keep reading about potential issues if [ and ] were to be allowed, but
the only *actual* issues I’m seeing are due to the fact that [ and ] are
_not_ allowed. It would be nice to have that balanced by someone who's
already tried it. (I may try it at some point in the future, but
haven’t got too much time for it atm).
Fossil does work perfectly both on Unix& Windows, but having those
funky characters (space included) in a filenames which are meant to be
kept under DVCS is *bad practice* both on Unix& Windows.
Why is that a bad practice? Because there's programs (like Fossil) that
won't let you work with them?
As I wrote earlier, not being able to have space in a tag name is much
severe limitation, but I do not hear many people complain about (g)it.
I reckon you don't hear so much people complain about spaces in tags
because it *isn't* a more severe limitation than disallowing (otherwise
perfectly valid) characters in file names.
Tags are something you add once you're using your SCM; also, you're free
to decide what kind of tag you want to use. Programmers have been
circumventing lack of spaces in identifiers for ages, by using
underscores, dashes, or by playing on capitalization.
Filenames, on the other hand, are often pre-existing, and you don't
always have the luxury of picking and choosing, since they are not
always created by you; worse, sometimes you don't even have the
possibility of imposing limitations on the characters used.
We've already seen that someone who wants to store OOXML files in a
'diff'-able way, will have to jump through extra hoops to get the
"[Content-Types].xml" file into fossil. I also run into this issue
every now and then, because someone in our office once long ago decided
to timestamp historical versions with the time and dates between square
brackets.
Our office's current VCS (PVCS/Serena ChangeMan) has no trouble at all
with [ and ], but then we routinely use the GUI interface. I haven't
used their command line interface extensively, so I don't know how it
fares then. Then again, it's on Windows, and AFAIK [ and ] have no
special meaning for cmd.exe -- certainly not if you quote the file names
(which is a good idea anyway, since spaces do occur from time to time).
Yours,
--
Martijn Coppoolse
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
