This is the mail archive of the
mailing list for the Cygwin project.
Re: version information for cygcheck
- From: Joshua Daniel Franklin <joshuadfranklin at yahoo dot com>
- To: Robert Collins <robert dot collins at itdomain dot com dot au>, cygwin-patches at cygwin dot com
- Date: Sun, 24 Feb 2002 07:42:35 -0800 (PST)
- Subject: Re: version information for cygcheck
>The usual thing to do for versions is to get the CVS version number and
I'm assuming that lines like this in CVS/Entries give the version numbers:
/cygcheck.cc/1.22/Tue Jan 29 03:08:42 2002/-ko/
/cygpath.cc/1.13/Thu Jan 17 16:54:01 2002/-ko/
/dump_setup.cc/1.4/Tue Jan 29 18:37:00 2002//
/dumper.cc/1.8/Fri Sep 14 15:07:31 2001//
/dumper.h/1.2/Thu Aug 30 16:47:51 2001//
/getfacl.c/1.5/Tue Jan 29 03:08:42 2002/-ko/
/kill.cc/1.10/Mon Oct 8 03:06:25 2001/-ko/
/mkgroup.c/1.9/Tue Jan 29 03:08:42 2002/-ko/
/mkpasswd.c/1.20/Thu Jan 31 12:43:29 2002/-ko/
I've got a problem then. Currently `cygpath --version` outputs 1.2, where it
should be 1.13 apparently. Is there a way to get the CVS version up to 1.21
with a patch? Also, if I add --version options to each util,
should I increment the version by .01 each time, so cygcheck will be v1.23,
mkgroup 1.91, etc.? I guess the question should be, does CVS automatically
increment the version by a certain amount after a patch?
Also, if I'm going to patch several files, should I tar up several
.cc-patch files or do one big patch?
Do You Yahoo!?
Yahoo! Sports - Coverage of the 2002 Olympic Games