info-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: address@hidden: Re: rename in cvs]


From: Greg A. Woods
Subject: Re: address@hidden: Re: rename in cvs]
Date: Sat, 13 Oct 2001 18:45:29 -0400 (EDT)

[ On Saturday, October 13, 2001 at 12:34:03 (-0700), Paul Sander wrote: ]
> Subject: Re: address@hidden: Re: rename in cvs]
>
> Greg A. Woods wrote:
> >
> > [ On Friday, October 12, 2001 at 20:34:48 (-0700), Paul Sander wrote: ]
> > > Subject: Re: address@hidden: Re: rename in cvs]
> > >
> > > They can be stored in newphrases inside the RCS files, without breaking
> > > compatibility.  It's still the wrong way to do it, but it's an improvement
> > > over the status quo.
> > 
> > Well, it could be, but that would break human compatability too, and
> > thus that's about the worst way to put such meta data.
> 
> Huh???  RCS and CVS can read the files (correctly, and modify them,
> correctly), and humans aren't supposed to touch the repository directly
> anyway.  And if humans know enough about the RCS file format, they know
> how to identify newphrases.  And the introduced newphrases will be
> documented, so humans who happen to read the files will still understand
> them.

Obviously you haven't thought through the long term consequences of
doing something like that, especially in face of a potentially very wide
diversity of how people might access a CVS repository.

"Hiding" such information inside the RCS file in a non-standard
extension, i.e. in a way that would make it invisible to "standard" RCS,
or CVS, is not a good idea for a generic solution.

-- 
                                                        Greg A. Woods

+1 416 218-0098      VE3TCP      <address@hidden>     <address@hidden>
Planix, Inc. <address@hidden>;   Secrets of the Weird <address@hidden>



reply via email to

[Prev in Thread] Current Thread [Next in Thread]