On Friday 15 January 2021 10:52:24 pm J Leslie Turriff wrote:
>
> So. I spent ~6 hours making changes to nsd_cccc.txt, and now I find that
> I'm spinning my wheels, because there are tools available to make the
> changes.
Hi Leslie,
Editing the source file (nsd_cccc.txt) to correct it so that it then can
generate all the other files without errors is usually how it's done. Git
does need to have the original nsd_cccc.txt somewhere for later updates, so
the mapping is generally like this:
nsd_cccc.original.{date}.txt
nsd_cccc.original.{date}.txt
nsd_cccc.edited.{date}.txt
nsd_cccc.edited.{date}.txt
e.g. nsd_cccc.edited.20210116-114406.txt
{date} is easier for follow up people, but many also use {revision} instead.
I personally don’t like {revision} as it’s too easy to typo (see Ref:).
The last nsd_cccc.edited.txt is used by the process (perl ./genstations.pl) to
generate the downstream files.
The nsd_cccc.original.{date}.txt are kept so that any new nsd_cccc.txt can be
diff’ed against the last nsd_cccc.original.{date}.txt to extract just what’s
changed so only those changes need to be merged into a new nsd_cccc.edited.
{date}.txt file.
You time has not been wasted! And thank you tons!
Best,
Michael
Ref: alias pd='echo $(date +"%Y%m%d-%H%M%S")'
____________________________________________________
tde-users mailing list -- users@xxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxx
Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@xxxxxxxxxxxxxxxxxx
