Re: File permissions

[Paul Sander]

>--- Forwarded mail from address@hidden

>[Greg A. Woods - Tue at 03:47:57PM -0400]
>> There's no way to handle _any_ file attribute change tracking without
>> extending the RCS file format.  Period.

>When PreservePermission is set, the information is actually written to the
>RCS files.  Is this a gross hack?  Does it break up RCS somehow?

>> Take it up with the RCS maintainers if you want to do something productive
>> about it.

>Is RCS still beeing developed at all?

>I see no reason why the frame of the RCS file format should be a definite
>blocker for what features there can be in CVS.  After all, if RCS was
>perfect, there would be no need for CVS?

>Information that won't fit into the ,v-files can be stored elsewere.  It
>adds complexity, and that's undesireable - but it's certainly possible.

The RCS file format also provides a way to extend the format without
breaking compatibility, both at the file and version levels.  Naming
conventions can provide a measure of protection from collisions in the
event that RCS files are shared between multiple version control systems
that both make extensions.

And since CVS writes the RCS files directly (i.e. without the benefit
of the RCS executables), it should not be difficult to add such extensions.

>--- End of forwarded message from address@hidden