Hi, all,

some people have bemoaned Fossil's lack of file permissions support over
the years. Initially, Fossil did not track _any_ permissions, but the
executable bit was eventually added because it is common practice to have
an executable configure script in the source tree.

What i didn't know, though, is that git doesn't, either. i always assumed
git can do anything except except for making me a happy user.

To quote the GIT Pocket Guide from O'Reilly[1]:

"Originally, Git saved and restored the full permissions on files (all the
mode bits). Later, however, this was deemed to cause more trouble than it
was worth, so the interpretation of the mode bits ... was changed ... the
only valid values for the low 12 bits of the mode... are octal 755 and 644,
and these simply indicate that the file should be executable or not... the
actual mode value may be different depending on your umask setting..."


[1] http://shop.oreilly.com/product/0636920024972.do

<http://shop.oreilly.com/product/0636920024972.do>--
----- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to