Public SourceMage Discussion List

[Juuso Alasuutari <iuso AT sourcemage.org>]

Alright, I've done this in test (e857822318d954c501e8d2ac072b6d4f2569098c) 
and 
z-rejected (eb18c8ccca873e27d0839f69c4dacf720d2fd866). 

Here's the script I used (without hardcoded name & email of course). I urge 
the maintainers of other grimoires to make use of it. Also it will come in 
handy the next time we do this kind of cleaning. (Run it in the grimoire root 
directory. You'll have to commit && push yourself, and please check the diff 
thoroughly before doing anything final.)

----5kr1p7 574r7----
#!/bin/bash

NAME="First Last"
EMAIL="email AT addre.ss"

FILES="$(grep -lr "^\ *PATCHLEVEL=[0-9][0-9]*\ *$" ./ | grep DETAILS)"
for i in $FILES; do
  if grep -qlr "^\ *UPDATED=[0-9][0-9]*\ *$" "$i"; then
    sed -i  "/^\ *UPDATED=[0-9][0-9]*\ *$/d" "$i"
    sed -i  "1i$(date +%Y-%m-%d) $NAME <$EMAIL>\n\t* DETAILS: \
[automated] Removed UPDATED (deprecated in favor of \n\t  PATCHLEVEL).\n" \
            "${i/\/DETAILS//HISTORY}"
  fi
done
----5kr1p7 3nd----

On Monday 14 August 2006 23:36, Arwed von Merkatz wrote:
> On Mon, Aug 14, 2006 at 11:27:17PM +0300, Juuso Alasuutari wrote:
> > On Monday 14 August 2006 23:13, Arwed von Merkatz wrote:
> > [snip]
> >
> > > I think removing UPDATED whenever a spell is updated or gets a new
> > > PATCHLEVEL/SECURITY_PATCH is the safer solution, even if it'll take
> > > some time.
> >
> > Removing UPDATED from those spells that already have PATCHLEVEL is
> > considered safe, then? There are 90 of these in test at the moment.
>
> That should be ok.

-- 
        Juuso Alasuutari
[[ Source Mage GNU/Linux ]]

Attachment: pgpgqA5m5U57J.pgp
Description: PGP signature