[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: cvs export usage text
From: |
Mark D. Baushke |
Subject: |
Re: cvs export usage text |
Date: |
Tue, 23 Nov 2004 12:22:11 -0800 |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Jerry.Nairn@microchip.com writes:
> Since export requires either a tag or a date:
Actually, you may combine a branch tag at a particular date, so
both "-r tag -D <date>" are permitted. It is NOT an either-or
semantic requirement, it is a one or both requirement.
> src/checkout.c
> line 69 (export usage message)
>
> the line:
> "Usage: %s %s [-NRfln] [-r rev] [-D date] [-d dir] [-k kopt] module...\n",
>
> should read:
> (a) "Usage: %s %s [-NRfln] [-r tag | -D date] [-d dir] [-k kopt]
> module...\n",
>
> or (gack!):
> (b) "Usage: %s %s [-NRfln] -r tag | -D date [-d dir] [-k kopt]
> module...\n",
>
> See the diff usage message for something like (a) above. It is not quite
> perfect since it seems to imply that a tag or date is not required, only
> mutually exclusive. The second example (b) could be misinterpreted as a
> pipe, however. I'm not sure what the proper usage message syntax would be.
>
> In the lines after that,
>
> " -r rev Export revision or tag."
>
> Is incorrect because export will not accept a numeric revision, only a
> tag.
> It should be:
> " -r tag Export a tag."
I suppose that this:
"Usage: %s %s [-NRfln] [-r tag] [-D date] [-d dir] [-k kopt] module...\n",
...
"\t-r tag\tExport tag (one of '-r tag' or '-D date' is required).\n"
"\t-D date\tExport revisions as of date.\n",
...
makes as much sense as anything... but I don't really like it.
> or:
> " -r tag Export revisions with a symbolic tag."
>
> or possibly:
> " -r tag Export a tag. Either '-D date' or '-r tag' must be specified."
Anyone have any better suggestions?
-- Mark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQFBo5vz3x41pRYZE/gRAnvSAJ9B9+pZfbVxyZkY8wMYLlFbgSw61ACdGdUf
KUQJrD07warwa/WMWjSjp9g=
=UBA9
-----END PGP SIGNATURE-----