C. Michael Pilato

Externals lines starting with '#' are ignored

Committed to trunk/en; backported to branches/1.7/en.

Merge from ^/trunk/en r6061.

Issue #284: Document the externals definitions comment syntax.

* ch03-advanced-topics.xml

I still have a lingering nag here. I assumed the executable bit was a feature of the filesystem, not of the OS. Yet, "system calls" are a feature of the OS. It's common to have, say, a FAT32 volume mounted in Linux. But does the reverse occur, where an ext3 filesystem is mounted in Windows? It sounds like APR won't try to set an executable bit on such a filesystem. What about network filesystems? Will APR preserve the executable bit on, say, an NFS mount when accessed via Windows?

As I read this, I believe the OP is not suggesting that Subversion behaves any differently than the book describes, but rather that the text misrepresents NTFS as not having a notion of an executable permission bit. Unfortunately, the proposed fix causes a different confusion by allowing an NTFS-knowledgeable person to assume that Subversion will conditionally set that bit on NTFS (which, of course, it does not). Perhaps the text could be changed to read instead: This property has no effect on Windows...

As I read this, I believe the OP is not suggesting that Subversion behaves any differently than the book describes, but rather that the text misrepresents NTFS as not having a notion of an executable permission bit. Unfortunately, the proposed fix causes a different confusion by allowing an NTFS-knowledgeable person to assume that Subversion will set that bit on NTFS (which, of course, it does not). Perhaps the text could be changed to read instead: This property has no effect on Windows or on filesystems...