[FFmpeg-devel] Patchwork instance running for FFmpeg-devel

Måns Rullgård mans
Sun Jan 23 15:08:24 CET 2011

Vitor Sessak <vitor1001 at gmail.com> writes:

> On 01/23/2011 01:35 PM, M?ns Rullg?rd wrote:
>> Vitor Sessak<vitor1001 at gmail.com>  writes:
>>> On 01/23/2011 01:18 PM, M?ns Rullg?rd wrote:
>>>> Vitor Sessak<vitor1001 at gmail.com>   writes:
>>>>> On 01/22/2011 06:01 PM, Janne Grunau wrote:
>>>>>> Hi,
>>>>>> http://patchwork.libav.org runs a patchwork instance
>>>>>> (http://ozlabs.org/~jk/projects/patchwork/) looking on FFmpeg-devel for
>>>>>> patches and comments. It's hooked into the git.ffmpeg.org/ffmpeg.git
>>>>>> repository and changes patch status on commits. This is currently not
>>>>>> working perfectly due to mismatches in commit messages.
>>>>>> I tried to send old mails to patchwork but due to the commit message
>>>>>> matching they weren't changed to 'Committed' from the rewritten svn
>>>>>> commit messages.
>>>>>> Everyone should be able to register an account for his email address and
>>>>>> will be able to change his own patches. Bug me to change the account to
>>>>>> FFmpeg maintainer which will be allowed to change all patches.
>>>>>> There is a patchwork command line client at
>>>>>> http://patchwork.libav.org/help/pwclient/ and config file at
>>>>>> http://patchwork.libav.org/project/FFmpeg-devel/pwclientrc/
>>>>>> The command line client makes applying ok-ed patches simple as:
>>>>>> pwclient view $PATCH_NUM | git am [-c] -s -
>>>>>> Please take care and look at the patch before applying. Some patches
>>>>>> are recorded with the full email. If that's the case the -c option to
>>>>>> 'git am' is handy.
>>>>>> I'm looking if it's possible to make status changes with emails which
>>>>>> would simplify the workflow. Patchwork seems to have trouble to
>>>>>> automatically superseede patches with refreshed versions.
>>>>> Would it be easy to import the old patches at
>>>>> http://wiki.multimedia.cx/index.php?title=Interesting_Patches ?
>>>> As easy as rebasing them to master and sending to this list.
>>> Is the rebasing really necessary? Doesn't patchwork accept patches
>>> that applies to older git revisions?
>> It would, but some of those patches are _very_ old and might not even
>> make sense anymore.  I'd rather not blindly throw them in there and
>> have them just take up space.
> If they don't deserve space the disk space in patchwork, it doesn't
> belong to the wiki page either.

I was thinking of screen space, not disk space.

M?ns Rullg?rd
mans at mansr.com

More information about the ffmpeg-devel mailing list