[FFmpeg-devel] [PATCH 2/2] doc/developer: s/ffmpeg-cvslog/ffmpeg-devel

Ganesh Ajjanagadde gajjanag at mit.edu
Sun Sep 20 03:15:34 CEST 2015


On Sat, Sep 19, 2015 at 9:09 PM, James Almer <jamrial at gmail.com> wrote:
> On 9/19/2015 10:03 PM, Ganesh Ajjanagadde wrote:
>> On Sat, Sep 19, 2015 at 8:30 PM, James Almer <jamrial at gmail.com> wrote:
>>> On 9/19/2015 8:54 PM, Ganesh Ajjanagadde wrote:
>>>> On Sat, Sep 19, 2015 at 7:48 PM, James Almer <jamrial at gmail.com> wrote:
>>>>> On 9/19/2015 8:36 PM, Ganesh Ajjanagadde wrote:
>>>>>> ffmpeg has not been using cvs for a long time.
>>>>>>
>>>>>> Signed-off-by: Ganesh Ajjanagadde <gajjanagadde at gmail.com>
>>>>>> ---
>>>>>>  doc/developer.texi | 2 +-
>>>>>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>>>>>
>>>>>> diff --git a/doc/developer.texi b/doc/developer.texi
>>>>>> index 7324629..923ee69 100644
>>>>>> --- a/doc/developer.texi
>>>>>> +++ b/doc/developer.texi
>>>>>> @@ -349,7 +349,7 @@ timeframe (12h for build failures and security fixes, 3 days small changes,
>>>>>>  Also note, the maintainer can simply ask for more time to review!
>>>>>>
>>>>>>  @item
>>>>>> -Subscribe to the ffmpeg-cvslog mailing list. The diffs of all commits
>>>>>> +Subscribe to the ffmpeg-devel mailing list. The diffs of all commits
>>>>>>  are sent there and reviewed by all the other developers. Bugs and possible
>>>>>>  improvements or general questions regarding commits are discussed there. We
>>>>>>  expect you to react if problems with your code are uncovered.
>>>>>
>>>>> https://ffmpeg.org/pipermail/ffmpeg-cvslog/
>>>>>
>>>>> ffmpeg-cvslog has a different purpose than ffmpeg-devel.
>>>>
>>>> Isn't the same information available at
>>>> https://ffmpeg.org/pipermail/ffmpeg-devel/?
>>>> Can you tell me what the difference between the two is?
>>>
>>> If you check and compare the emails between the two list, you'll notice that one
>>> is a list where automated emails are sent every time something is committed to
>>> the git repo, and the other is a list where patches are sent for review.
>>
>> Well, in that case the doc is broken in a worse way. "Bugs and
>> possilbe improvements or general questions regarding commits are
>> discussed there" does not even apply to ffmpeg-cvslog, it really
>
> Discussion about commits (not patches) can and does happen there, even though in
> general it's always CCd to ffmpeg-devel where people are more likely to see it.
> ffmpeg-devel has its own section on this file, mentioning it's meant for patches
> and discussions about development.

Thanks for clarifying. I still think it is terribly confusing; the
very fact that we are discussing this right now suggests that it needs
rework. I will let this sink in and may come up with an improvement
sometime. At the moment, consider the patch dropped.

>
>> applies to ffmpeg-devel. In that case this patch is still an
>> improvement over the current situation. ffmpeg-cvslog is pretty much
>> useless for a dev on daily basis, since he/she can't see the
>> discussion. If a dev is subscribing to something, ffmpeg-devel gives
>> far more useful information and IMHO is the preferred mailing list.
>>
>> However, perhaps the commit message needs rewording due to my misunderstanding.
>
>
>
> _______________________________________________
> ffmpeg-devel mailing list
> ffmpeg-devel at ffmpeg.org
> http://ffmpeg.org/mailman/listinfo/ffmpeg-devel


More information about the ffmpeg-devel mailing list