[FFmpeg-cvslog] r22522 - in trunk: configure libavcodec/Makefile libavcodec/dsputil.c libavcodec/dsputil.h libavcodec/dwt.c libavcodec/dwt.h libavcodec/ivi_dsp.c libavcodec/snow.c libavcodec/snow.h libavcodec/x86/...

[Alex Converse]

On Sun, Mar 14, 2010 at 7:21 PM, Michael Niedermayer <michaelni at gmx.at> wrote:
> On Sun, Mar 14, 2010 at 05:00:34PM -0400, Alex Converse wrote:
>> On Sun, Mar 14, 2010 at 4:50 PM, Michael Niedermayer <michaelni at gmx.at> wrote:
> [...]
>> > you can checkout with svn per date/time instead of revission then it
>> > will get a matching revission for all externals
>> >
>>
>> Which is great until someone gives you revision number and you need to
>> reverse it into a timestamp. And if there are automated tools that can
>> do this then why can't svn-co do it?
>
> ask the svn devels ...
>
>
>>
>> Furthermore SVN doesn't have any bisecting support so the point is
>> somewhat moot.
>>
>> > also as we are speaking about a git switchover, if we choose to do this
>> > please dont do it during gsoc, it would just make work harder to students
>> > to learn a new vcs.
>> >
>>
>
>> Having worked on the aac-sbr code base which was set up like one of
>> our soc projects, ditching our awful soc-svn repository format in
>> favor of a real git branch easily doubled my productivity.
>
> like changing the variable names from random 2 letter names to
> english words would have halfed it
>

With the exception of patch construction and a few other routines
described only in flowchart form, the variable names are constructed
to follow a scheme and are perfectly understandable without looking at
the spec.

I challenge you to try to do you H.264 refactoring in an soc style
topic branch in SVN for two months... If you aren't too busy trying to
find fonts less readable than the ones you use now.

Suggesting our students use svn *in the manner svn has historically
been used by our SoC projects* is one of the biggest disservices we
can provide to them.