Release errata & patch list

[George Georgalis]

On Mon, Apr 25, 2005 at 02:02:15PM -0400, Justin C. Sherrill wrote:
>> 	It can definitely be done with an awk and a minimal shell script.
>>
>> 	Similar to the way I used to generate FreeBSD-4 MFC lists, which
>> 	I did my regex'ing the commit mail archive.  I will see if I can
>> 	do something for branch commits and put it up on leaf.
>
>It can be added relatively easily to the existing mailarchive script - the
>mail's already getting passed through there, anyway.
>
>Something like: (not tested, won't work)
>
>:0b
>* ^Newsfetch: \/dragonfly.commits
>* MATCH ?? Branch: \/(DragonFly_RELEASE_\d_\d) {
>    BRANCH=$MATCH
>    echo $body | cat >> /path/to/webpage/for/$BRANCH
>}
>
>I can tackle this, if you like.
>


As an aside, I've been meaning to script up a process for mirrors to
keep cvs/cvsup current, whereby the commit emails trigger a cvsup from
the master of the updated module as often but not more than :20 minutes
or so, then maybe a full sync every 24 hrs for sanity.

But no being my primary OS, and needing to make my first cvsupd mirror
and a few other elements (including unrelated commitments), I've not
moved forward on this. I'm stuck where I create cvsupd config files,
couldn't those just be included in cvs where they can be used directly?
(ATM I forget the default location)

I'd also considered triggering a module rsync from leaf for my own local
cvs repository copy... but that would require compiling rsync there....

Is there a better way to go about this (low latency, low bandwidth,
current cvs/cvsupd mirrors)? Doesn't FBSD or OBSD have a scheme for
mailing patches when they are committed, and scripts to apply?

// George


-- 
George Georgalis, systems architect, administrator Linux BSD IXOYE
http://galis.org/george/ cell:646-331-2027 mailto:george at xxxxxxxxx