[darcs-users] short options and long names (VOTE!)

[Kenneth Knowles]

My votes:

On Sat, May 29, 2004 at 06:19:47AM -0400, David Roundy wrote:
>      --summary               summarize changes

I use this all the time, so a short option would be cool... I see -s is taken by
--sign, but I'd rather use it for summary (I'm quite biased, having never used
send)

>   -A EMAIL      --author=EMAIL          specify author id
>   -T EMAIL      --to=EMAIL              specify destination email
>   -V PUBRING  --verify=PUBRING          verify that the patch was signed by a key in PUBRING
>   -c EMAIL      --cc=EMAIL              specify email address to cc
>   -s            --sign                  sign the patch with your gpg key

Most of the email control options don't seem like they need short options to me.
A main rationale being that only options that are either used constantly, or
similar to other unix programs are likely to be used (if you have to look at -h
output as a reminder, you probably don't mind using the long option).  Also,
when configuring it via your email client then I'd tend to use long options to
make the script self-explanatory.

>   -a            --all                   answer yes to all patches
>   -g            --gui                   use graphical interface
>   -h  --help                shows brief description of command and its arguments
>   -m PATCHNAME  --patch-name=PATCHNAME  name of patch
>   -o FILE       --output=FILE           specify output filename
>   -r  --recursive           add contents of subdirectories
>   -t TAGNAME    --tag-name=TAGNAME      name of version to pull
>   -u                                    pass -u option to diff
>   -u            --unified               output patch in format similar to diff -u
>   -v            --verbose                 give verbose output

In case anyone votes to remove any of these, I'll pre-emptively counter-vote
that these are really good short options.

Kenn