> It makes some sense in principle, but without storing what they mean
> (i.e., group==?) it certainly makes no sense.
There's no "they" there.
I think Martin's proposal, to which I agreed, was to store a _single_
bit. If any of the execute permissions of the incoming file are set,
then the bit is stored ON, else it is stored OFF. On 'checkout', if the
bit is ON, then the file permission is set mode 0777 (modulo umask),
else it is set mode 0666 (modulo umask).
You might disagree that this is a good idea, but it certainly does
'make sense' (as in 'is sensibly well defined').
> I suspect a non-readable file would cause a bit of a problem in the low-level
Probably so. If someone sets their umask 0333 or less, then they are
either fools or QA (software quality assurance, or test) engineers.
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <[EMAIL PROTECTED]> 1.650.933.1373,
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html