Larry Jones wrote:
> [EMAIL PROTECTED] writes:
>
> > I think that 'at least' names of entities in the CVS repository should
> > be held (or at least parsed into) canonical form. These are (almost)
> > opaque cookies the CVS server stores on the client system, not client data.
>
> If CVS treated those as binary files instead of text files (which is
> what you're proposing, whether you know it or not), then on some
> platforms you wouldn't be able to (conveniently) use a text editor to
> fix them when someone moves the repository. I'm not sure I'm willing to
> pay that price.
That's a good point I hadn't considered.
It does have an obvious rebuttal: As I understand it the only text file
conventions we are worried about are the three different EOLs. What is stopping
us from writing the db files natively from whatever platform but allowing any of
the three line endings when reading them in?
Of course I think the answer may be that this solves some problems while
encouraging others - namely that it may created a false belief that using a
workspace shared across NFS is now safe or that FTP'ing your workspace between
Windows & UNIX is safe.
Of course, applying this modification to .cvspass might be reasonable. Then a
user could use the same $HOME under UNIX & DOS usefully...
Derek
--
Derek Price CVS Solutions Architect ( http://CVSHome.org )
mailto:[EMAIL PROTECTED] OpenAvenue ( http://OpenAvenue.com )
--
War doesn't determine who's right. War determines who's left.
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
