[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: need help understanding underlying file format for cvs
From: |
Larry Jones |
Subject: |
Re: need help understanding underlying file format for cvs |
Date: |
Sun, 9 Mar 2003 13:18:37 -0500 (EST) |
Mark D. Baushke writes:
>
> cvs should be upward compatible with RCS format. The only thing that is
> an extension is the use of a 'magic branch number' which uses a '.0.' as
> the second rightmost position in a version number (ie, 1.1.0.2 is a
> 'magic branch number'). See the cvs documentation at
>
> http://www.cvshome.org/docs/manual/cvs_5.html#SEC59
>
> for more details.
That doesn't really affect the format, just how it's interpreted.
> I believe that there must be one or more occurances of a {delta} element
> in a cvs repository's representation of a ,v file. Likewise for the
> deltatext being one or more occurances.
While CVS will not normally create a file with no deltas or deltatexts
(unless something goes seriously wrong), I don't think it has any
problem reading them.
> cvs does not use newphrase at the present time, but I think it may properly
> ignore it...
I think the notoriously buggy PreservePermissions code uses newphrase's
to store the permission and type information.
-Larry Jones
The authorities are trying to silence any view contrary to their own!
-- Calvin
- need help understanding underlying file format for cvs, Ronald Petty, 2003/03/08
- Re: need help understanding underlying file format for cvs, Mark D. Baushke, 2003/03/09
- Re: need help understanding underlying file format for cvs,
Larry Jones <=
- Re: need help understanding underlying file format for cvs, Ronald Petty, 2003/03/09
- Re: need help understanding underlying file format for cvs, Larry Jones, 2003/03/10
- Re: need help understanding underlying file format for cvs, Derek Robert Price, 2003/03/21
- Re: need help understanding underlying file format for cvs, Mark D. Baushke, 2003/03/21
- Re: need help understanding underlying file format for cvs, Shaun Tancheff, 2003/03/22