[FFmpeg-devel] Patch Manager (Re: Roundup being migrated)
Sun Feb 15 11:46:37 CET 2009
2009/2/15 Mike Melanson <mike at multimedia.cx>:
> Robert Swain wrote:
>> 2009/2/15 Mike Melanson <mike at multimedia.cx>:
>>> Do I have crontab privileges on mphq? (Checking... 'crontab -e' works).
>>> I should be able to come up with an automated monitoring solution for
>>> /incoming. I'm thinking of something along the lines of:
>>> * initialize database of all files in incoming/, along with their timestamps
>> Database eh? Off-topic, but I'd like some sort of patch management
> You know I'm all about the databases. Let's talk.
>> system that is:
>> - Patches pending review
>> - Patches that have been reviewed but need to have issues addressed
>> - Patches that have been OKed but need to be applied
>> So that one doesn't have to trawl through the mailing list to see if
>> there are OKed patches waiting to have regressions tests run and be
>> applied. A link to the mailing list thread might be handy for figuring
>> out a commit message and giving credit though.
> I have been looking at creating some database-driven websites using any
> one of a number of web frameworks in existence. This should make a good
> exercise as well.
> Incidentally, if anyone has any specific experiences with particular web
> frameworks, let me know.
What do you want to discuss? :) I thought of the idea because I know I
often miss unapplied patches because I don't read every single e-mail
or thread that comes through this mailing list. I tend to visually
filter out stuff relating to AAC and other things of interest.
Diego always seems to know of patches that have been OKed but not
committed though I'm not sure how. When I suggested having something
onto which Michael could drop OKed patches or hunks, he didn't give
away any secrets. :)
Even if it were just a stack of links to threads with OKed patches,
that would work too.
More information about the ffmpeg-devel