-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Frank Hemer wrote:
|> Also, .commitid.next as currently defined should be nonsense in |> almost all cases. Only .commitid & .commitid.prev are |> meaningful. | | | Thats right. However it would require extra code to prevent this, | and I don't really think this will cause problems. I assume a user | who is willing to type such a number probably knows what he's | doing?;-)
I agree. I didn't mean to suggest prohibiting it.
| As an extension to my doc: If no files are specified (recursive | calls or calls on a flat dir), all combined tags need to be | absolute. '.base.next' is invalid here, because it depends on the | specific file's rev number and subconsequently cannot serve as a | dirtag (on commands like update ...). '.trunk.prev' would be ok | here. So if applied on directories, a tag needs to start with | either a numeric rev. num, '.trunk', '.commitid' or a symbolic tag. | .base should apply recursively from a workspace.
Regards,
Derek -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (Cygwin) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCMbrALD1OTBfyMaQRAjQ2AJ9hzfbaR2YnOvPfHUVDZIWxk8RkaACg8VAg tMb5A7y3V1GUrZObtyW13jY= =dyAq -----END PGP SIGNATURE-----
_______________________________________________ Bug-cvs mailing list Bug-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/bug-cvs
