Judson Lester <jlester@tulane.edu> writes:
> Actually, the convention I've seen more often than not is that the
> serial number be a concatenation of the date, with the last two digits
> being for multiple changes on the same day (YYMMDDCC). Depending on
> when the cron job runs, you could probably avoid reading the old file
> and just produce the date concatenation with either a low change
> number or a high change number, and a comment about what the script
> does so that any by-hand changes can play nice.
Correct. That is exactly how I do serial numbers and it is a highly
recommended approach. actually a 4 digit year is better. That's what
I was recommending -- modifying h2n to parse the serial number, incrementing
according to standard in place in the local environment, and include that
updated serial number in it's final output. I would bet there are
other scripts available that already do this. Google and CPAN would
be of help here ;)
-- Scott Harney<scotth@scottharney.com> "...and one script to rule them all." gpg key fingerprint=7125 0BD3 8EC4 08D7 321D CEE9 F024 7DA6 0BC7 94E5
___________________
Nolug mailing list
nolug@nolug.org
This archive was generated by hypermail 2.2.0 : 12/19/08 EST