-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Larry Jones wrote:
>Mark D. Baushke writes:
>
>>I like the idea of `-r <tag>:<datespec>' in general.
>>
>>However, it becomes harder for things like cvs log where
>>`-r <tag>:<token>' already treats <token> as rev2.
>>This means that
>>
>> cvs log -rmytag:now
>>
>>would be ambiguous. Is 'now' a tag or a time?
>
>
>I think that's where we got stuck the last time we danced around this
>issue.
What about some simple workaround like using a different delimiter in
date specs? I'm loath to use `|' due to the shell quoting problems, and
slash might cause some confusion in conjunction with dates
(`mytag/2004/04/02' looks potnentially confusing but it isn't actually
ambiguous...).
Hrm... Just thought of something... any colons in a date spec's time
field could still become confusing in conjunction with the log command,
regardless. Perhaps the best thing to do would be to switch the
delimiter in the log spec (the colons in `-r myfirsttag::mysecondtag')
to `!' or `+' or whatever. None of the potential delimiters really
strike me as The Right Thing (tm), yet, but we could just pick
something. Then if the new delimiter appears anywhere in the argument
to `log -r' or if there are more than two colons that aren't consecutive
characters, then the parser would expect the new form.
Of course, we could also decide to not include the -rtag:date form in
conjunction with log at all, perhaps only as a temporary solution, but I
don't like that idea much.
Derek
- --
*8^)
Email: [EMAIL PROTECTED]
Get CVS support at <http://ximbiot.com>!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Using GnuPG with Netscape - http://enigmail.mozdev.org
iD8DBQFAbXh0LD1OTBfyMaQRAsCCAKCcF21201muJfFWVaCjxqYG+LsYJACgk1np
l7vvxX5a+Bvha8r0aDZ1ZL4=
=jrSE
-----END PGP SIGNATURE-----
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
