-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Derek Price <[EMAIL PROTECTED]> writes:
> I thought Mark was just saying earlier in this
> thread that .trunk.root, by virtue of .root
> normally specifying a revision on the parent
> branch, should refer to the `0' revision?
Hmmm... I may be getting confused, I thought
.trunk.root.prev would be the `0' revision,
but if you are right then .trunk.root.next
would be the same as .origin right?
As for `0', we probably need to be more consistent
about it... for example, the command:
cvs rdiff -r0 -r1.1 foo-module/foo-file
yeilds a diff against /dev/null of the foo-file
while the commands
cvs co foo-module && cd foo-module && cvs diff -r0 -r1.1 foo-file
yeilds an error message:
'cvs diff: tag 0 is not in file foo-file'
this probably needs to be `fixed' to do something
reasonable with `0' for most uses as a phantom
revision that exists before the file existed on
the branch or trunk.
-- Mark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQFCJ0QA3x41pRYZE/gRAtxLAKDKCpFooWEpuPrQ+QKaZFWKntp8jwCgg/st
m5sIT/JB03xZC4SdQDnRBYk=
=R37G
-----END PGP SIGNATURE-----
_______________________________________________
Bug-cvs mailing list
Bug-cvs@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-cvs
