On Wed, 2003-04-09 at 09:11, Scott Harney wrote:
> 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 ;)
I update my serial numbers all at once with this script:
#!/bin/sh
# first ls > files and delete the ones you don't want to update
for file in `cat files`
do
ed $file <<-EOF
H
g/serial/s/[0-9]\+/2003040903/
w
q
EOF
done
>
> Craig Jackson
> Wildnet Group L.L.C.
> 103 North Park, Suite 110
> Covington, Louisiana 70433
> 985 875 9453
___________________
Nolug mailing list
nolug@nolug.org
Received on 04/09/03
This archive was generated by hypermail 2.2.0 : 12/19/08 EST