-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Mark D. Baushke wrote:
| 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?
No. I think 0.next would be an invalid construct, or also return 0.
If you take this off the trunk, this might make more sense: BRANCH.root is on the trunk (or another branch), so BRANCH.root.next would return the revision following the root revision on the parent. For example, 1.2.2.7.root would return 1.2. Since 1.2.next yields 1.3, then 1.2.2.7.root.next should also yield 1.3.
Since there is no revision following on the `0 branch', .trunk.root.next should either also be 0 or be invalid.
| 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.
I agree.
Regards,
Derek -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (Cygwin) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCJ0c2LD1OTBfyMaQRAj0dAJ9Qt/gkL2Vunx6y6A0GB4qxF+rqCwCgjrtr EnCQIIQjVKK4dNM8unXhwAY= =3dZx -----END PGP SIGNATURE-----
_______________________________________________ Bug-cvs mailing list Bug-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/bug-cvs
